google-authenticator-exporter VS extract_otp_secrets

I just migrated to aegis from Google. I used https://github.com/krissrex/google-authenticator-exporter Which requires you to have nodejs on a computer.

Here's the link: https://github.com/krissrex/google-authenticator-exporter

This library uses the GPL v3 license: https://github.com/scito/extract_otp_secrets?tab=GPL-3.0-1-o...

Your options are to either go open-source or remove the library.

I used https://github.com/scito/extract_otp_secrets to export the keys from the Google Authenticator and imported them manually into Bitwarden.

You can extract plaintext secret keys from google authenticator app and store them in user friendly format/password manager

https://github.com/scito/extract_otp_secrets

you can actually export them using tools like this one

I recently switched from Google Authenticator to Raivo and I used the export option in google auth and this tool to get the seeds.

Getting the code out of Google Authenticator is not trival. If you are good with python, someone has written a script to do that https://scito.ch/content/extract-secret-keys-google-authenticator-qr-export. However, with 17, you may be better off just doing it manually.

Try this: https://scito.ch/content/extract-secret-keys-google-authenticator-qr-export

I was able to take a screenshot of GAuth backups on iPhone using the button hotkeys(IE: Power+Volume up). I setup a container that runs a go version of GAuth and used a python script to decrypt the (decrypted QR code) backup keys. Then I backed up the encrypted keyfile to offline disk, encrypted the container backup and deleted it from the hypervisor.

https://github.com/pcarrier/gauth

https://github.com/scito/extract_otp_secret_keys

I used the "zbarimg" command line tool to get the inputs for the following Python tool (see README for instructions) from each QR code exported from Google Authenticator. https://github.com/scito/extract_otp_secret_keys