-
Notifications
You must be signed in to change notification settings - Fork 34
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(fdo-manufacturing-client): Support command line option for DI_SIGN_KEY_PATH and DI_HMAC_KEY_PATH #476
base: main
Are you sure you want to change the base?
Conversation
9c5923d
to
4e73d0c
Compare
I did not add those options since I'm usure of the values that they should take. Can you provide an example? |
Sorry if you already might know but these values (keys) are stored in device credential. You can follow the code The device credential stores the keys at last as: You can dump the secrets by |
Yes, my question is about how a user would generate those secrets. What type of keys are they? How do I generate them? |
Oh, I see. Sorry for my misreading. I hope below answers your question. hmac_key_path:
sign_key_path
|
I'm just going to see what we can do for #477 before I merge this. |
b9dd88a
to
ed1ccc7
Compare
Alright, I updated the docs https://github.com/nak3/fido-device-onboard-rs/blob/add-key-path-option/HOWTO.md#plain-di |
As `fdo-manufacturing-client plain-di` does not have the option for `DI_SIGN_KEY_PATH` and `DI_HMAC_KEY_PATH`, we need to specify it via env variable. This patch support the command line option.
This patch updates HOWTO docs with how to generate the private keys. Signed-off-by: Kenjiro Nakayama <[email protected]>
As
fdo-manufacturing-client plain-di
does not have the option forDI_SIGN_KEY_PATH
andDI_HMAC_KEY_PATH
, we need to specify them via env variable.This patch support the command line option.