Preston Van Loon prestonvanloon

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

GPG / Mutt / Gmail

About

This is a collection of snippets, not a comprehensive guide. I suggest you start with Operational PGP.

Here is an incomplete list of things that are different from other approaches:

I don't use keyservers. Ever.
Yes, I use Gmail instead of some bespoke hipster freedom service

Quick GPG Smartcard Guide

We will generate a master key with only the Certify capability and three subkeys with each of the Sign, Encrypt and Authenticate capabilities. These latter three keys are meant for daily use and will be transferred to an OpenPGP smartcard, which has three corresponding slots. The master private key can then be moved to offline cold storage, or stored on a second smartcard.

We are generating keys on a secure computer instead of on the card, because it allows more flexibility. Ideally this means a machine running Tails or one that is air-gapped and not connected to the internet.

This guide assumes that if you want to sign other peoples keys, then you will require the aforementioned secondary smartcard with your master key stored in its Signature slot, or if you only have one smartcard, then you'll have to fetch the master key out of cold storage. By default, GPG generates a master key with the Certify and

YubiKey 4 series GPG and SSH setup guide

Written for fairly adept technical users, preferably of Debian GNU/Linux, not for absolute beginners.

You'll probably be working with a single smartcard, so you'll want only one primary key (1. Sign & Certify) and two associated subkeys (2. Encrypt, 3. Authenticate). I've published a Bash function which automates this slightly special key generation process.

First, generate a JSON file of 64 unencrypted private keys in a common directory:

mkdir /tmp/keys
bazel run //tools/unencrypted-keys-gen -- --num-keys 64 --output-json /tmp/keys/val_1.json

Then, run the Eth1-Mock-RPC server:

bazel run //:eth1-mock-rpc -- --genesis-deposits 64 --unencrypted-keys-dir /tmp/keys

HP Smart Storage Admin CLI (`ssacli`) installation and usage on Proxmox PVE (6.x)

Why use HP Smart Storage Admin CLI?

You can use ssacli (smart storage administrator command line interface) tool to manage any of supported HP Smart Array Controllers in your Proxmox host without need to reboot your server to access Smart Storage Administrator in BIOS. That means no host downtime when managing your storage.

CLI is not as convenient as GUI interface provided by BIOS or desktop utilities, but still allows you to fully manage your controller, physical disks and logical drives on the fly with no Proxmox host downtime.

ssacli replaces older hpssacli, but shares the same syntax and adds support for newer servers and controllers.

	The remote desktop session has to be headless :(

	- Install the deb (can convert with alien & co)
	- Patch with modern_distro.diff (cherry-pick what your system needs)
	- To support automatic desktop resizing:
	- Works with any window manager
	- Build Xvfb with xvfb-randr.diff
	- Expose as /usr/bin/Xvfb-randr
	- If replacing system-wide binary by repackaging, simply
	# ln -sf Xvfb /usr/bin/Xvfb-randr

	#!/bin/bash

	# Copyright © 2017 Google Inc.
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software

	# Generate the private and public keys
	openssl ecparam -name secp256k1 -genkey -noout \| openssl ec -text -noout > key

	# Extract the public key and remove the EC prefix 0x04
	cat key \| grep pub -A 5 \| tail -n +2 \| tr -d '\n[:space:]:' \| sed 's/^04//' > pub

	# Extract the private key and remove the leading zero byte
	cat key \| grep priv -A 3 \| tail -n +2 \| tr -d '\n[:space:]:' \| sed 's/^00//' > priv

	# Generate the hash and take the address part

	#!/bin/bash

	# Copyright © 2017 Google Inc.
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software