-
-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for importing FreeOTP 2.0 encrypted backups #1084
Comments
Sounds good to me, feel free to submit a PR! (And indeed, the fact that FreeOTP now uses the Android Keystore for encryption means that we probably can't import directly from the app's internal storage anymore. Importing the backup file should be possible, though) |
wow freeotp got an update? I thought it was abandoned! |
What would this require technically? As an user, it seems like FreeOTP encrypted backups creates a file called To load the FreeOTP backup into Aegis, all that seems to be needed is the main passphrase that was entered into FreeOTP when first installing the app (or upgrading to v2+). For implementation details, perhaps the FreeOTP codebase can show how to make the import of decrypted backups. Since FreeOTP uses the Apache 2 license, it should be possible to include code inspired by FreeOTP (for example related to handling encryrpted backups) in Aegis. |
I took a quick look at this today, but I don't think we'll be adding support for this until freeotp/freeotp-android#381 is addressed. |
just to confirm, there's no functional way to import from freeotp at all atm (not just backups), as the original reporter and alex suspected. the 'import from app' route tries to import from a file called tokens.xml that doesn't exist any more, if you copy tokenStore.xml to tokens.xml it fails with a bunch of errors about missing algo and secret values. might be good to change the title of this issue to make the scope clearer? |
Only import from FreeOTP 2.0 and newer doesn't work. We've added a hint to allude to this (#1204) but perhaps there are a couple more places where we should make this explicit. Patches welcome. |
Include the '(1.x)' qualifier directly in the import-source selection dropdown to avoid raising false expectations. See also: - beemdevelopment#1204, where the 1.x-hint was introduced - beemdevelopment#1084: tracking issue for 2.x support - freeotp/freeotp-android#381 FreeOTP-issue to reconsider the brittle serialised java format used by 2.x
In version 2.0, FreeOTP gained the ability to export backups. The backups are encrypted and Aegis is currently unable to import them.
Additionally, 2.0 update notes say that tokens were migrated to KeyStore. As far as I understand, this might mean that the old method of importing the xml file no longer works.
The text was updated successfully, but these errors were encountered: