Initially taken by Niko Matsakis and lightly edited by Ryan Levick
- Introductions
- Cargo inside large build systems
- FFI
- Foundations and financial support
FROM archlinux:20200205 AS arch-ghc-build-env | |
RUN pacman -Syu --noconfirm | |
RUN pacman -S --noconfirm git base-devel go python python-sphinx libedit numactl exa | |
# use all possible cores for subsequent package builds | |
RUN sed -i 's,#MAKEFLAGS="-j2",MAKEFLAGS="-j$(nproc)",g' /etc/makepkg.conf | |
# don't compress the packages built here | |
RUN sed -i "s,PKGEXT='.pkg.tar.xz',PKGEXT='.pkg.tar',g" /etc/makepkg.conf | |
# set up the packager user |
use std::str; | |
fn main() { | |
// -- FROM: vec of chars -- | |
let src1: Vec<char> = vec!['j','{','"','i','m','m','y','"','}']; | |
// to String | |
let string1: String = src1.iter().collect::<String>(); | |
// to str | |
let str1: &str = &src1.iter().collect::<String>(); | |
// to vec of byte |
use std::time::{ Instant, Duration }; | |
fn benchmark<F: FnOnce()>(f: F) { | |
let t0 = Instant::now(); | |
f(); | |
let t1 = Instant::now(); | |
let dt = t1 - t0; | |
println!("{}", dt.as_millis()); | |
} |
function dockershell() { | |
docker run --rm -i -t --entrypoint=/bin/bash "$@" | |
} | |
function dockershellsh() { | |
docker run --rm -i -t --entrypoint=/bin/sh "$@" | |
} | |
function dockershellhere() { | |
dirname=${PWD##*/} |
// | |
// Example: Hello World! | |
// | |
// This is an example UEFI application that prints "Hello World!", then waits for key input before | |
// it exits. It serves as base example how to write UEFI applications without any helper modules | |
// other than the UEFI protocol definitions. | |
// | |
// The `efi_main` function serves as entry-point. Depending on your target-configuration, this | |
// entry point might be called differently. If you use the target-configuration shipped with | |
// r-efi, then `efi_main` is the selected PE/COFF entry point. |
#!/usr/bin/env python | |
import subprocess | |
import re | |
from collections import namedtuple | |
import binascii | |
import time | |
import json | |
IGNORE = """ | |
nm-applet |
jq will sort (-S
) the whole file (.
) and compare STDOUT (<()
) with diff
diff <(jq -S . A.json) <(jq -S . B.json)
XML processing modules may be not secure against maliciously constructed data. An attacker could abuse XML features to carry out denial of service attacks, access logical files, generate network connections to other machines, or circumvent firewalls.
The penetration tester running XML tests against application will have to determine which XML parser is in use, and then to what kinds of below listed attacks that parser will be vulnerable.
Enter this in the search box along with your search terms:
Get all gists from the user santisbon.
user:santisbon
Find all gists with a .yml extension.
extension:yml
Find all gists with HTML files.
language:html