search

paolostivanin / OTPClient

Highly secure and easy to use OTP client written in C/GTK3 that supports both TOTP and HOTP
GNU General Public License v3.0
472 stars 46 forks source link

TOTP codes generated from Aegis backup are incorrect #178

Closed alanorth closed 4 years ago

alanorth commented 4 years ago

I imported a plain, unencrypted JSON Aegis backup into OTPClient, but it seems the codes generated are different than those generated by Aegis itself. I've had two sites now ask for 2FA and reject the code generated by OTPClient, only to go find my phone and use the code from Aegis successfully.

I'm using OTPClient version 2.3.0 from Flatpak. Thanks!

paolostivanin commented 4 years ago

If installed from the distro's repo, then it works. So it must be something related to flatpak... :thinking: I'll look into it

alanorth commented 4 years ago

I just updated the Arch Linux AUR version to v2.3.1 and I confirm that the codes imported from Aegis are correct now. I have uninstalled the flatpak version.

paolostivanin commented 4 years ago

EDIT: false alarm. I wasn't able to reproduce it, I made a mistake

paolostivanin commented 4 years ago

Weird. I was able to reproduce it using flatpak-builder on my dev machine, but on a newly installed system the flatpak version works just fine :astonished:

alanorth commented 4 years ago

OK so you have some debugging to do. Bummer! I will stick to the non-Flatpak version from AUR now that I got it updated to v2.3.1 (and also I'll ask the derelict maintainer to assign the package to me). You can close this issue if you like. Cheers!

paolostivanin commented 4 years ago

Ok, I'll close this and put a memo on the other issue. Thanks for your work :+1:

paolostivanin commented 4 years ago

closing and merging with #179