-
Notifications
You must be signed in to change notification settings - Fork 70
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
The point of the create-keys -e and -d options? #278
Comments
Please see #258 |
Please see #258
Maybe rather #259 directly? I don't see how either answers my interrogations, to be honest, esp. not why there would be 2 distinct options if the GUID file and keys subdir always have to live in the same directory.
Either way, this is cosmetics as long as the directory does not have to be accessible to the bootloader. If it does, /boot would be a better choice, IMHO.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the point of being able to create keys in a non-default location if the other commands only look in the default location? (I would store the keys on
/boot
)Also, it seems you need to use both
-e
and-d
; in any case just using-d
raises an error.The text was updated successfully, but these errors were encountered: