-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat(custom-keys): roll out any bytes to the specificed hierarchy #239
Conversation
Signed-off-by: Fabian Wienand <fabian.wienand@9elements.com>
Signed-off-by: Fabian Wienand <fabian.wienand@9elements.com>
I might be missing something, but this is not really useful for general use of wanting to manage valid secureboot keys and should be possible using |
We already have |
Sure, I was not sure if that would be best as the command already has a bunch of different options, but I can incorporate the functionality into it 👍 |
In general, I agree with you, but i would like to put one additional flag inside the enroll-keys command to roll out invalid/empty/... keys for testing purposes. The convenience of sbctl as a pure-go tool is beneficial for some environments. |
Signed-off-by: Fabian Wienand <fabian.wienand@9elements.com>
semi-forgot this in the middle of work and camp 🙃 Generally I don't mind adding specialized flags to |
Generally, I think I should spend more time fixing the plumbing inside https://github.com/Foxboron/sbctl/blob/master/cmd/sbctl/status_test.go Otherwise, LGTM. |
Thanks! |
Use-Case: Testing that SecureBoot keys with a invalid signature or signing date must not be added to the efi.