-
Notifications
You must be signed in to change notification settings - Fork 6
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
Allow existing password to be used instead of generated one #4
Comments
True. I manually filled in |
Oh. Maybe
Thoughts/preference? |
I was thinking that of a separate setup operation, e.g. otp.py --init-password seed [--force] Also it could always prompt for a password if none exists; empty reply means generate. |
How about I do like the idea of prompting, and then generate if [return] is pressed (rather than silent generation). (and maybe error if anything entered is less than (say) 10 characters) |
I added --force to allow a user to correct a stored password. |
Gotcha. I have an aversion to Given that, I'd suggest something like Thanks! |
Given that the password may not be recoverable if it is replaced, I think it would be best if it required an extra option to allow an existing one to be overwritten. |
It might be useful to allow users to specify the initial password for a seed.
This would allow migration from another password database.
The text was updated successfully, but these errors were encountered: