hamsolodev

Dec  8 16:59:47 turmoil uwsgi: *** Starting uWSGI 1.9.20 (64bit) on [Sun Dec  8 16:59:47 2013] ***
Dec  8 16:59:47 turmoil uwsgi: compiled with version: 4.8.1 on 08 December 2013 15:21:26
Dec  8 16:59:47 turmoil uwsgi: os: Linux-3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013
Dec  8 16:59:47 turmoil uwsgi: nodename: turmoil
Dec  8 16:59:47 turmoil uwsgi: machine: x86_64
Dec  8 16:59:47 turmoil uwsgi: clock source: unix
Dec  8 16:59:47 turmoil uwsgi: detected number of CPU cores: 1
Dec  8 16:59:47 turmoil uwsgi: current working directory: /
Dec  8 16:59:47 turmoil uwsgi: detected binary path: /usr/local/bin/uwsgi
Dec  8 16:59:47 turmoil uwsgi: !!! no internal routing support, rebuild with pcre support !!!

hamsolodev

[uwsgi]
socket = /tmp/app.sock
chdir = /home/USER/sites/site.com/repo.git

env = NEW_RELIC_ENVIRONMENT=production
env = NEW_RELIC_CONFIG_FILE=newrelic.ini

uid = USER
chown-socket = www-data:GROUP
chmod-socket = 660

hamsolodev

Nice illustration of importance of MAC use in encryption

Without use of MAC, it’s easy to mess with the IV to change the result of “successfully decrypting” ciphertext.

First, create some plaintext:

echo Give Eve \$500 > plaintext.dat

cat plaintext.dat

hamsolodev

My ThinkPad X200 Arch Linux install process

TODO passphrase protected keyfiles…setup a keyfile in a remaining key-slot? something to make this properly two–factor.

Notes on installing Arch Linux from scratch, using LVM volumes inside a LUKS container.

Why not boot from removable media? Well, there's no real support for “plausible deniability” built in to LUKS/dm-crypt. This means that the benefit of booting from removable media—being able to keep secret the fact that the main HDD contains an encrypted

hamsolodev

# -*- coding: utf-8 -*-
#
# Retrieve a list of hosts from EC2, with Name metadata tags matching
# the supplied regex.
#
# e.g. in your fabfile
#
#     env.roledefs = {
#         'somesite': lambda: matching_names(r'somesite-web-\d+'),
#        }

hamsolodev

# -*- mode: sh; coding: utf-8 -*-
# check for interactive shell, returning straight away if this isn't
# one!
[ -z "$PS1" ] && return

setopt prompt_subst
setopt transient_rprompt
setopt prompt_sp

autoload -Uz vcs_info

hamsolodev

#!/usr/bin/env python
# -*- coding: utf-8 -*-
#
# Update Route53 DNS A name record for home IP.
#
# Uses the *route53* library, rather than boto.
import os
import re
import sys

hamsolodev

remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L

hamsolodev

My ThinkPad X200 Arch Linux install process

TODO passphrase protected keyfiles…setup a keyfile in a remaining key-slot? something to make this properly two–factor.

Notes on installing Arch Linux from scratch, using LVM volumes inside a LUKS container.

Why not boot from removable media? Well, there's no real support for “plausible deniability” built in to LUKS/dm-crypt. This means that the benefit of booting from removable media—being able to keep secret the fact that the main HDD contains an encrypted

hamsolodev

Watch outgoing DNS requests on wlan0

tcpdump -pni wlan0 'port domain'