Justin Schmitz Justin-Schmitz

Keybase proof

I hereby claim:

I am justin-schmitz on github.
I am shmeetz (https://keybase.io/shmeetz) on keybase.
I have a public key ASA2jfT_11yjU1iStwAPxMERrjokUjZQ6BmzosPY5-4iDgo

To claim this, I am signing this object:

Ansible

Understanding Ansible

Ansible is a powerful, simple, and easy to use tool for managing computers. It is most often used to update programs and configuration on dozens of servers at once, but the abstractions are the same whether you're managing one computer or a hundred. Ansible can even do "fun" things like change the desktop photo or backup personal files to the cloud. It can take a while to learn how to use Ansible because it has an extensive terminology, but once you understand the why and the how of Ansible, its power is readily apparent.

Ansible's power comes from its simplicity. Under the hood, Ansible is just a domain specific language (DSL) for a task runner for a secure shell (ssh). You write ansible yaml (.yml) files which describe the tasks which must run to turn plain old / virtualized / cloud computers into production ready server-beasts. These tasks, in turn, have easy to understand names like "copy", "file", "command", "ping", or "lineinfile". Each of these turns into shell comma

Build docker image

$ cd /path/to/Dockerfile
$ sudo docker build .

View running processes

docker-compose cheat sheet

Reference: https://docs.docker.com/compose/compose-file/#compose-file-structure-and-examples

Collection of a few docker-compose examples which I use regularly

Instructions on using docker-compose files

# docker-compsoe version to be used must be mentioned at the top 
version: '3'
services:

	export TERM="xterm-256color" # This sets up colors properly

	# workaround as per https://superuser.com/questions/1222867/zsh-completion-functions-broken
	FPATH=$HOME/.oh-my-zsh/plugins/git:$HOME/.oh-my-zsh/functions:$HOME/.oh-my-zsh/completions:/usr/share/zsh/site-functions:/usr/share/zsh/$ZSH_VERSION/functions

	export FPATH

	# set shell
	export SHELL=/usr/bin/zsh

	/*
	* m1cat: a proof of concept for the M1RACLES vulnerability in the Apple M1.
	*
	* This program implements a covert channel that can be used to transmit data
	* between two processes when run on the Apple Silicon "M1" CPUs.
	*
	* The channel is slightly lossy due to (presumably) the scheduler sometimes
	* scheduling us on the wrong CPU cluster, so this PoC sends every byte twice
	* together with some metadata/framing bits, which is usually good enough.
	* A better approach would be to use proper FEC or something like that.

	/*
	* m1racle-poc: a basic proof of concept for the M1RACLES vulnerability in the Apple M1.
	*
	* This program allows you to read and write the state of the s3_5_c15_c10_1 CPU register.
	*
	* Please visit m1racles.com for more information.
	*
	* Licensed under the MIT license.
	*/