fboender

#!/usr/bin/env python3

import sys
import os
import subprocess
import json


class CmdError(Exception):
    def __init__(self, msg, exitcode, stderr):

fboender

#!/bin/bash

# A script for setting audio video profiles and launching applications. For
# example, since my webcam is in my laptop. I'd like my Google Meet window to
# be on the laptop too, so I can look at the webcam.

set -e

declare -A SCREEN_LAYOUTS
declare -A SCREEN_COORDS

fboender

"----------------------------------------------------------------------------
" Look
"----------------------------------------------------------------------------
syntax on           " Syntax color highlighting powah
set nowrap          " Do not wrap text at window width
set hlsearch        " Highlight search matches
set laststatus=2    " Always display file status line
set number          " Show line numbers.
set hidden          " Allow changing buffers with changes in them
set background=dark " Dark background

fboender

Moving Authy to 1Password

1Password 5.3 for OSX, 5.2 for iOS, and 4.1.0.538 for Windows support OTP. I've been using Authy for a while now, but the fact is, I haven't really been using 2FA for some time. As mentioned by 1Password in a recent blog post, having the OTP generator and password on the same device is very much not 2FA. It's just an expiring OTP, which can help, but let's not kid ourselves too much.

With that out of the way. One of the things that was interesting to me was moving my OTP out of Authy and into 1Password. I like the control I get with 1Password, but I didn't want to have to reset all my OTP right away, that would suck. So, I got to dissecting the Authy Chrome App to see what I could do.

Run the Authy Chrome app and make sure it's unlocked.

Now, enable Developer mode in Chrome. We'll need this to inspect the background application that stores al

fboender

Generating Authy passwords on other authenticators

---

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

fboender

Keybase proof

I hereby claim:

• I am fboender on github.
• I am fboender (https://keybase.io/fboender) on keybase.
• I have a public key ASD88WiXeZYuYBGHnWvFe_SG1pzvDkGPkwpf10FPwozIZQo

To claim this, I am signing this object:

fboender

<?xml version="1.0"?>
<FbDirectInvoice xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<Element>
		<Fields Action="insert">
			<OrDa>2014-07-01</OrDa>     <!-- Datum -->
			<DbId>50028</DbId>          <!-- Debiteurnummer -->
			<RfCs>12345</RfCs>          <!-- Referentienummer -->
			<Re>Opmerking</Re>
			<War>*****</War>            <!-- Magazijn - Verwijst naar Logistiek / Voorraad / Magazijn -->
            <DeCo>14</DeCo>             <!-- Betalingsvoorwaarde - Verwijst naar Algemeen / Inrichting / Instellingen betalingen / Betaalvoorwaarde -->