Skip to content
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 "Aegis plain text export" file imports #128

Closed
RichyHBM opened this issue Sep 28, 2022 · 5 comments
Closed

Support "Aegis plain text export" file imports #128

RichyHBM opened this issue Sep 28, 2022 · 5 comments
Milestone

Comments

@RichyHBM
Copy link

Is your feature request related to a problem? Please describe.
When wanting to migrate from external apps to 2fauth it can be quite cumbersome without having to redo all your tokens

Describe the solution you'd like
A method of batch importing all tokens from external apps, in particular Aegis text format files, the creation of these can be found here, this could be done with just a command line script to add these to the database, wouldn't need to be a new UI

@Bubka
Copy link
Owner

Bubka commented Sep 28, 2022

Hi Richy,

Great proposal, 2FAuth already supports Google Auth import, so it makes sens to add more data source.
Could you paste here the content of a typical Aegis plain text export file (with redacted values).

Thanks

@RichyHBM
Copy link
Author

From what I understand it is the same format as a google authenticator text file export, all I could see in the docs regarding google exports was via QR code, are google plain text files supported for input? Will try get some sample exports

@Bubka
Copy link
Owner

Bubka commented Sep 28, 2022

The Export feature of Google Authenticator for Android provides plain text file?! I'm surprised. AFAIK, on iOS, it has always been a QR code. Furthermore, the GA QR code encodes a protobuf payload.

That said, if the Aegis Export feature provides QR codes based on the GAuth format then you can flash those QR codes with 2FAuth, it should work.

@RichyHBM
Copy link
Author

I'm actually not sure now, I just read in the Aegis docs that it outputs as google authenticator format, maybe thats outdated tho. Here is an example of the contents of one of the export files with 4 entries:

otpauth://totp/Example%3Aalice%40google.com?period=30&digits=6&algorithm=SHA1&secret=JBSWY3DPEHPK3PXP&issuer=Example
otpauth://totp/Apple%3Asomeone%40test.com?period=30&digits=6&algorithm=SHA256&secret=K5UHG2DE&issuer=Apple
otpauth://steam/steam%3Asteamuser?period=30&digits=5&algorithm=SHA1&secret=K5UHG2DE&issuer=steam
otpauth://totp/Google%3Atest%40name.com?period=30&digits=6&algorithm=SHA512&secret=K5UHG2DE&issuer=Google

@Bubka
Copy link
Owner

Bubka commented Sep 28, 2022

Indeed this is a plain text format. I think they speak about Google Auth format because each line use the otpauth URI format, which has been introduced by Google Auth to easily carry OTP data in a single string.

I take the request, it should be available in the next 2FAuth release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Released
Development

No branches or pull requests

2 participants