I hereby claim:
- I am horzadome on github.
- I am horzadome (https://keybase.io/horzadome) on keybase.
- I have a public key whose fingerprint is 9B4A 7E7B 2BE0 0F2D CC9F DECB 46CD 370A 976E B07E
To claim this, I am signing this object:
#!/bin/bash | |
# Author: Davor Grubisa for Igor Tomljanovic | |
# v01. Davor Grubisa horzadome@gmail.com - written it | |
# Replace this wrkdir line with /etc when ready | |
wrkdir=$HOME/testing | |
outfile=hosts.allow | |
tmpfile=hosts.allow.tmp | |
cd $wrkdir | |
touch $outfile |
I hereby claim:
To claim this, I am signing this object:
There is an increasing count of applications which use Authy for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.
Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. I couldn't find any completely working solutions, however I stumbled upon a gist by Brian Hartvigsen. His post had a neat code with it to generate QR codes for you to use on your favorite authenticator.
His method is to extract the secret keys using Authy's Google Chrome app via Developer Tools. If this was not possible, I guess people would be reverse engineering the Android app or something like that. But when I tried that code, nothing appeared on the screen. My guess is that Brian used the
# Update Hurricane Electric IPv6 Tunnel Client IPv4 address | |
# This is an upgrade to an existing script from | |
# http://wiki.mikrotik.com/wiki/Hurricane_Electric_IPv6_Tunnel_-_IPv4_Endpoint_updater | |
# API call format: | |
# https://#USERNAME:$API_KEY@ipv4.tunnelbroker.net/nic/update?username=$USERNAME&password=$API_KEY&hostname=$TUNNEL_ID | |
# ---------------------------------- | |
# Modify the following to match your parameters | |
# ---------------------------------- | |
# Router's WAN interface name |