-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Feature Request: Export from CLI #187
Comments
Good idea, I'll add it to the list :) |
I'm sure this isn't really high priority, but any idea when this might be implemented (so when version 3.0.0 would release)? |
Hello! |
That would be awesome - I'll keep my eye out for 2.4.0, thanks! |
It's now possible to export the data directly from the CLI. As it is for the GUI, data can be export to andotp (only encrypted), freeotpplus and aegis format. This fixes #187
It's now possible to export the data directly from the CLI. As it is for the GUI, data can be exported in andotp, freeotpplus and aegis format. This fixes #187
It's now possible to export the data directly from the CLI. As it is for the GUI, data can be exported in the andotp, freeotpplus and aegis format. For andotp, both encrypted and plain json formats can be chosen. This fixes #187
If you want, you can test branch |
That branch doesn't exist :) But I see a 2.4.0 tag plus it is in master. I tested it out and it seems to work, so that's great. But I have another request for this, which I'll open as a new issue! |
Cool, thanks for double checking! |
Would it be possible to add a export feature that can be called from the CLI? I'd like to make automatic backups of my OTP codes to an encrypted directory as part of a broader backup script I use for myself. Ideally I could make an otpclient backup integrated so that I don't have to manually export the file. I'd like to run the command in a bash script and then be prompted from my password before exporting (to Aegis JSON, for my use case).
The text was updated successfully, but these errors were encountered: