BigFoxses

import multiprocessing #:)

def do_this(number):
  print number
  return number*2

# Create a list to iterate over. 
# (Note: Multiprocessing only accepts one item at a time)
some_list = range(0,10)

BigFoxses

#!/usr/bin/env python
import argparse


def main(command_line=None):
    parser = argparse.ArgumentParser('Blame Praise app')
    parser.add_argument(
        '--debug',
        action='store_true',
        help='Print debug info'

BigFoxses

set -e, -u, -x, -o pipefail

The set lines

• These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing.
• With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.

• set -euxo pipefail is short for:

set -e
set -u

BigFoxses

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no

BigFoxses

#include <mach/mach.h> // mach_task_self, vm_protect
#include <substrate.h> // MSFindSymbol


// MARK: - Types

typedef void (*MSHookMemory_ptr_t)(void *target, const void *data, size_t size);

#define ENSURE_KERN_SUCCESS(ret) \ 
if (ret != KERN_SUCCESS) { \

BigFoxses

QEMU + Ubuntu ARM aarch64

These are the steps I used to get Ubuntu ARM aarch64 running with QEMU on OSX.

Get Ubuntu Image and QEMU EFI:

wget https://cloud-images.ubuntu.com/releases/16.04/release/ubuntu-16.04-server-cloudimg-arm64-uefi1.img
wget https://releases.linaro.org/components/kernel/uefi-linaro/latest/release/qemu64/QEMU_EFI.fd

BigFoxses

#! /bin/bash
#
# build-xnu-4903.221.2.sh
# Initial script by Brandon Azad (https://gist.github.com/bazad/654959120a423b226dc564073b435453)
# Updated on 12/11/18 by matteyeux
# 
# A script showing how to build XNU version 4570.1.46 on MacOS High Sierra
# 10.13 with Xcode 9.
#
# Note: This process will OVERWRITE files in Xcode's MacOSX10.13.sdk. Make a

BigFoxses

Check Bitcode

It is important to enable Bitcode in all libraries if the app is going to enable Bitcode. These scripts check each static library for Bitcode and echo a string which shows up as a warning in the build log. It is an easy way to always check that the dependencies have what is needed.

Usage

Place check_bitcode.sh in your project directory. Then add a Run Script in Build Phasese with the script named RunScript.sh. Name that new section as Check Bitcode and run the build. It may be necessary to make the shell script executble using chmod u+x check_bitcode.sh on the command-line.

Frameworks vs Static Libraries

BigFoxses

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

BigFoxses

#
# Demonstrating kSecKeyAlgorithmECIESEncryptionCofactorX963SHA256AESGCM
#
# David Schuetz (@DarthNull)
# May 2018
#
# see also: https://darthnull.org/security/2018/05/31/secure-enclave-ecies
#

###############################################################