JP Bochi jpbochi

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

There are always 24 hours in a day.
February is always 28 days long.
Any 24-hour period will always begin and end in the same day (or week, or month).

This is a quick guide of the commands we use to sign someone's GPG key in a virtual key signing party.

Note: The steps cover only the technical aspects of signing someone's key. Before signing someone's key, you must verify their identity. This is usually done by showing government-issued ID and confirming the key's fingerprint

The commands will work for both GPG and GPG2.

I use Julian's key for the examples. His key id is 2AD3FAE3. You should substitute with the appropriate key id when running the commands.

Signing the key

List the keys currently in your keyring: gpg --list-keys.

ANSI Escape Sequences

Standard escape codes are prefixed with Escape:

Ctrl-Key: ^[
Octal: \033
Unicode: \u001b
Hexadecimal: \x1B
Decimal: 27

https://coderwall.com/p/4j4azg/pair-program-anywhere-with-tmux-over-ssh-tunnel

https://github.com/roburio/pf-firewall/blob/master/TODO

ssh -R 2222:localhost:22 [email protected]

The local user would open a tmux session specifying a shared socket:

tmux -S /tmp/pair new-session -s pairing; chmod 0777 /tmp/pair

	# will not work in all cases, see https://gist.github.com/angelo-v/e0208a18d455e2e6ea3c40ad637aac53#gistcomment-3439904

	function jwt-decode() {
	sed 's/\./\n/g' <<< $(cut -d. -f1,2 <<< $1) \| base64 --decode \| jq
	}

	JWT=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ

	jwt-decode $JWT

	#!/usr/bin/env bash
	set -eu

	log () {
	echo >&2 "[lock] $@"
	}

	putLock () {
	aws s3api put-object --region $REGION --bucket $BUCKET --key $LOCK_KEY --output text --query 'VersionId'
	}

	#!/usr/bin/env sh
	set -eu

	API_BASE="${API_BASE:-https://github.api.manage.rackspace.com}"

	KEY_FILE=${KEY_FILE:-"$HOME/.ssh/id_rsa"}

	fail() {
	echo >&2 "This tool needs an SSH key to sign a request to $API_BASE."
	echo >&2 "The key must be configured as a deploy key in your GitHub repository linked to an AWS account."

	#!/bin/zsh
	#
	# Purpose: run specified command with specified arguments and cache result. If cache is fresh enough, don't run command again but return cached output.
	# Also cache exit status and stderr.
	# Copyright (c) 2019-2023 András Korn; License: GPLv3

	# Use silly long variable names to avoid clashing with whatever the invoked program might use
	RUNCACHED_MAX_AGE=${RUNCACHED_MAX_AGE:-300}
	RUNCACHED_IGNORE_ENV=${RUNCACHED_IGNORE_ENV:-0}
	RUNCACHED_IGNORE_PWD=${RUNCACHED_IGNORE_PWD:-0}

	# from https://stackoverflow.com/questions/2180270/check-if-current-directory-is-a-git-repository
	[ -d .git ] \|\| git rev-parse --git-dir > /dev/null 2>&1