-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
net: Add credentials shell #64343
net: Add credentials shell #64343
Conversation
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.
There are quite a few compliance reports, please look them over.
0e6b7fe
to
00a04e9
Compare
653e78d
to
0123f2d
Compare
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.
Sorry for the delay, I wrote comment yesterday, but messed something up and GH did not publish them...
TBH that's a way better place to cross-link anyways, will do. |
66574de
to
66447f0
Compare
Did the docs build time out? Gonna try another force push |
0397156
to
6d92d71
Compare
Adds an internal credential_digest for generating a string digest of credentials. Such digests would allow users of a prospective TLS credentials shell to verify the contents of a given credential without directly accessing those contents. Offloading the digest process to the underlying backend allows backends for which private portions are not directly accessible to be eventually supported. Signed-off-by: Georges Oates_Larsen <[email protected]>
Add (internal) support for sectag iterating. Also officially marks negative sectag values as reserved for internal use. This will allow a prospective TLS credentials shell to iterate over all available credentials. Signed-off-by: Georges Oates_Larsen <[email protected]>
6d92d71
to
31728cb
Compare
@glarsennordic Please check the compliance, it reported some nits. |
Adds a shell interface for TLS Credentials, allowing management of credentials via the Zephyr shell Signed-off-by: Georges Oates_Larsen <[email protected]>
31728cb
to
f8a9d39
Compare
A late comment: @glarsennordic you may want to configure your text editor for enforcing the max 100 char line limit for .rst content, as the added page definitely fell through the cracks. Thanks! |
@kartben Sorry, it is standard practice where I work for .rst files to exceed 100 chars, and for each sentence to exist on a single line, and for each line to have only a single sentence. I assumed that was the same with Zephyr, is that not the case? I notice there is inconsistency on this within the Zephyr docs. Some |
Yeah that'd be a nice thing to have and have one less thing on the reviewer to keep an eye on. |
I am not familiar enough with the checkpatch script to evaluate how easy it would be to take exceptions into account. There will always be some tables, really long URLs etc that will have to be treated as exceptions. I should look into https://pypi.org/project/doc8/ linter again though... |
Nah forget checkpatch, the idea is to phase it out, look for https://github.com/zephyrproject-rtos/zephyr/blob/main/scripts/ci/check_compliance.py, the |
Thanks for the heads-up! I might give doc8 a serious try (plus, it can be used programmatically which is nice). The only somewhat tricky but will be to only flag the errors that are related to the lines that were touched. |
None of our checks does that at the moment, you may have to bite the bullet and fix all files before deploying, that's how it went for yamllint. |
Well checkpatch does work on the diff and the diff only, does it not? |
It does, but Perl :-) |
These commits introduce a TLS credentials shell allowing credentials to be installed and managed from any shell backend