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

UX: rage-keygen error output can be more intuitive #530

Open
Supermarcel10 opened this issue Sep 22, 2024 · 0 comments
Open

UX: rage-keygen error output can be more intuitive #530

Supermarcel10 opened this issue Sep 22, 2024 · 0 comments

Comments

@Supermarcel10
Copy link

General Info

The error message was not as intuitive as it could have been.

It would be more intuitive for the keygen to create a directory if one doesn't exist for the file, or at the very least mention that the directory does not exist rather than it failing to open.

As this improvement could be undesirable for the user or cause issues, it would be worthwhile to also have a flag to prevent creation of any directories (if applicable for the user).

What were you trying to do

I was trying to generate a new key pair.

What happened

The console output:

~$ rage-keygen -o ~/.config/age/age.key
Error: Failed to write to output: Failed to open file '/home/marcel/.config/age/age.key'

[ Did rage not do what you expected? Could an error be more useful? ]
[ Tell us: https://str4d.xyz/rage/report  

The output implies that a file exists which is trying to be opened.

What I had to do instead was create the directory manually with mkdir, and then create the key pair file within it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant