← Back to context

Comment by denkmoon

2 years ago

Haha, I see you manically rage posting in this topic. I empathise, it's fucking shit when "smart" people foist something unwanted on you because they think it's better for you. FWIW, I'm feeling pretty liberated to have moved my OTP codes out of authy and into multiple locations - my data, as much as I'd prefer not to use it, is now under my control.

You can get the old desktop version from chocolatey/choco - https://community.chocolatey.org/packages/authy-desktop/

If anyone wants to try this themselves, this is the recipe that worked for me;

- Enable multi device for authy on my phone

- Install the 3.0 desktop authy client from chocolatey

- Get logged in and set up on the desktop client so that you can see the current OTP codes (not the lock symbol)

- Uninstall the 3.0.0 desktop authy client

- Install the 2.2.3 desktop authy client from chocolatey (https://community.chocolatey.org/packages/authy-desktop/2.2.... or choco install authy-desktop --version=2.2.3)

- DISCONNECT FROM THE INTERNET AFTER OPENING 2.2.3 AND BEFORE IT POPS THE UPDATE DIALOG

- The update dialog will block the program and you can't use the chrome remote debugger in the later steps

- Start from step 2 of https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d...

It is not worked now. If I tried to log in, the message popped up, "The device does not meet the minimum integrity requirements".

Thank you for the time you took to write this out. I'm sure it'll help people. It would probably work if I used Windows, but I don't.

Great comment. Authy seems to be taking a user hostile stance by taking hostage peoples OTP's this way.