I hereby claim:
- I am msimkins on github.
- I am mikesimkins (https://keybase.io/mikesimkins) on keybase.
- I have a public key ASBMTKW2iOA7WcGbjeC0NmO_eYtvKBiJyTFnE1Q3XQIJ1wo
To claim this, I am signing this object:
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 (beware, through Google) 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 gues
#!/bin/sh | |
send_slack() { | |
if [ -z "${SLACK_TOKEN}" ];then | |
echo "function send_slack needs SLACK_TOKEN variable. Add a new integration to slack." | |
exit 1 | |
fi | |
if [ -z "${1}" ];then | |
echo "No text to send ? Are you kidding me ?" |