-
Notifications
You must be signed in to change notification settings - Fork 33
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
--genkey option creation #35
Comments
Since a user of command line tool may be expected to generate their own keys using openssl, I am inclined to keep this option out of nostr console. This will simplify the tool and keep key generation separate from console - the user will know its their job to create and save their keys. |
I understand your position, but for the sake of simplicity, having to just use one tool instead of several is a plus in terms of user experience, IMHO (think of new comers). Theses keys could be stored in a ad-hoc .dotdir for nostr_console. Providing a single point of entry. |
A --genkey option should be a plus to avoid asking user to create their Private Key manually with
At start a dotfile must be searched if not existing, then a Warning must be written (if not Error instead).
When private key is created and stored in dotfile, then dotfile should be verified to be owned by the user and file mode must be 600.
The text was updated successfully, but these errors were encountered: