-
Notifications
You must be signed in to change notification settings - Fork 28
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
el2g: add documentation for GENERIC_KEYPAIRS #611
Conversation
lmp-el2go-auto-register was extended with support for generic keypairs. Document this new feature, in particular that GENERIC_KEYPAIRS has to be set in /etc/default/lmp-el2go-auto-register. Signed-off-by: Arnout Vandecappelle <[email protected]> Signed-off-by: Arnout Vandecappelle <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some minor suggestions, otherwise it looks good to me. Thanks for this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only some minor suggestions.
source/user-guide/el2g.rst
Outdated
Installing additional Secure Objects | ||
------------------------------------ | ||
|
||
Any additional Secure Objects that are defined in EdgeLock 2GO and provisioned into the secure element when the device registers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence is a bit off to me. I think the purpose here is to say that any additional secure objects <....> can be installed, or maybe list which are the expected additional objects. I think something is missing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The and should be are. But the sentence is still off. How about:
Additional Secure Objects can be defined in EdgeLock 2GO through the API.
These objects are provisioned into the Secure Element when the device registers.
Co-authored-by: Katrina Prosise <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I applied all suggested changes but have questions about the other comments.
source/user-guide/el2g.rst
Outdated
Installing additional Secure Objects | ||
------------------------------------ | ||
|
||
Any additional Secure Objects that are defined in EdgeLock 2GO and provisioned into the secure element when the device registers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The and should be are. But the sentence is still off. How about:
Additional Secure Objects can be defined in EdgeLock 2GO through the API.
These objects are provisioned into the Secure Element when the device registers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @arnout !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple suggestions related to other feedback.
Co-authored-by: Katrina Prosise <[email protected]>
Was it a good idea to merge this already? It documents a feature added in foundriesio/meta-lmp#1307 and that hasn't been merged yet (or received any feedback, actually). |
It will be okay. We can poke @rsalveti to merge it soonish - and it will all get released at the same time when the next LmP comes out. |
lmp-el2go-auto-register was extended with support for generic keypairs in PR foundriesio/meta-lmp#1307. Document this new feature, in particular that
GENERIC_KEYPAIRS
has to be set in/etc/default/lmp-el2go-auto-register
.Readiness
Overview
Why merge this PR? What does it solve?
Checklist
make linkcheck
.-s, --signoff
).-S, --gpg-sign
).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.