Florent Hemmi florenthemmi

Keybase proof

I hereby claim:

I am florenthemmi on github.
I am florenthemmi (https://keybase.io/florenthemmi) on keybase.
I have a public key ASDQzqLAadt97Xx73ghJsIU-1DLnZXn-pAIQ_TZuaoKi6go

To claim this, I am signing this object:

GPG and git on macOS

Setup

No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.

Install https://gpgtools.org -- I'd suggest to do a customized install and deselect GPGMail.
Create or import a key -- see below for https://keybase.io
Run gpg --list-secret-keys and look for sec, use the key ID for the next step
Configure git to use GPG -- replace the key with the one from gpg --list-secret-keys

Exporting (iCloud) Keychain and Safari credentials to a CSV file

After my dad died, I wanted to be able to have access any of his online accounts going forward. My dad was a Safari user and used iCloud Keychain to sync his credentials across his devices. I don’t want to have to keep an OS X user account around just to access his accounts, so I wanted to export his credentials to a portable file.

This is the process I used to create a CSV file of his credentials in the format “example.com,user,pass”. This portable format would be pretty easy to import into 1Password or Safari in the future.

The way I went about this isn’t great; it opens up more opportunities for apps to control one’s Mac through Accessibility APIs, it writes plaintext passwords to disk, and it could use some cleaning up. A better approach might leverage the security command line tool that ships with OS X. That said, I found this method to be a fun illustration of what’s possible us

	#
	# Acts as a nginx HTTPS proxy server
	# enabling CORS only to domains matched by regex
	# /https?://.*\.mckinsey\.com(:[0-9]+)?)/
	#
	# Based on:
	# * http://blog.themillhousegroup.com/2013/05/nginx-as-cors-enabled-https-proxy.html
	# * http://enable-cors.org/server_nginx.html
	#
	server {

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else