Sourav Ghosh mrghosh

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.

In experience to get a proper working multiple wan configuration using mwan3 starting from scratch you should:

Important: this works well on OpenWRT 15.05.1, on newer versions there was some breaking changes, for example, the wan ifaces have ipv6 capability and now are named with letters ("wan, wanb... , wanc" instead of "wan, wan2... wan3" so wanb6 means 2nd wan ipv6.): https://github.com/openwrt/packages/blob/master/net/mwan3/files/etc/config/mwan3

The official documentation seems to be very detailed and up to date, I recommend reading those first: https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3 but I recommend to give a look at my config file below, since my approach for policyes is very nice.

First of all: Activate conntrack, docs says that is important and neccesary to get MWAN3 work properly, and it is needed to reboot:

The netfilter hooks in the kernel and where they hook in the packet flow

The figure below calls out

The netfilter hooks
The order of table traversal

Workarounds for Netflix and the blocking of Hurricane Electric IPv6 tunnels

The dreaded "You seem to be using an unblocker or proxy." error message. Cool story bro.

This gist was essentially created out of my own rant about Netflix being hostile to IPv6 tunnel services since June 2016. You are welcome to read my opinion on the matter, this is the more technical side to the issue and how to combat it within your own network.

Since I wrote this, various GitHub users have contributed their thoughts and ideas which has been incorporated into this gist. Thank you to everyone who have contributed their own methods and implementations.

The problem

Netflix now treats IPv6 tunnel brokers (such as Hurricane Electric) as proxy servers. A while ago it became apparent to users and Netflix that somewhat by accident, IPv6 tunnel users were being served content outside of their geolocation because of the way Netflix was identifyi

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

	#!/system/bin/sh
	#
	echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra
	echo 1 > /proc/sys/net/ipv6/conf/default/disable_ipv6
	echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra
	echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
	echo 0 > /proc/sys/net/ipv6/conf/wlan0/accept_ra
	echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
	sleep 3
	echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra

	#!/bin/bash
	#
	# Digital Ocean Ubuntu 18.04 x64 Droplet with "Regular Intel" CPU.
	# Running:
	# git clone https://gist.github.com/54fc09734a3911e91eeeb43434f117df.git
	# cd 54fc09734a3911e91eeeb43434f117df/
	# chmod +x make-chr.sh
	# ./make-chr.sh
	#
	# Once the reboot is done, login with root/CHANGEME and change the password!

	#!/bin/ash
	#
	# angry_wifi.sh
	#
	# auto disconnects clients with a low signal strength on LEDE / OpenWRT. great
	# for clients who hold onto a lower-signal-strength accesspoint instead of
	# roaming. before running, make sure to download the latest MAC addresses with:
	#
	# wget --no-check-certificate -O - 'https://services13.ieee.org/RST/standards-ra-web/rest/assignments/download/?registry=MAC&text=apple' \| cut -d, -f2 > apple_mac_addresses
	#

	\n
	============= HOST: ==========\n
	\n
	local_ip: %{local_ip}\n
	local_port: %{local_port}\n
	remote_ip: %{remote_ip}\n
	remote_port: %{remote_port}\n
	\n
	======= CONNECTION: ==========\n
	\n

	#!/bin/bash

	# As the "bufferbloat" folks have recently re-discovered and/or more widely
	# publicized, congestion avoidance algorithms (such as those found in TCP) do
	# a great job of allowing network endpoints to negotiate transfer rates that
	# maximize a link's bandwidth usage without unduly penalizing any particular
	# stream. This allows bulk transfer streams to use the maximum available
	# bandwidth without affecting the latency of non-bulk (e.g. interactive)
	# streams.