Update OTP section for programming a device specific private key #2672
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lurch
reviewed
Oct 26, 2022
documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc
Outdated
Show resolved
Hide resolved
lurch
reviewed
Oct 26, 2022
documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc
Outdated
Show resolved
Hide resolved
lurch
reviewed
Oct 26, 2022
documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc
Outdated
Show resolved
Hide resolved
lurch
reviewed
Oct 26, 2022
documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc
Outdated
Show resolved
Hide resolved
timg236
force-pushed
the
otp-device-specific-private-key
branch
from
9ad7747 to
26ba0f7
Compare
aallan
added
the
ready to merge
lurch
reviewed
Oct 26, 2022
documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc
Show resolved
Hide resolved
lurch
reviewed
Oct 26, 2022
| 46 -- WVC1 decode key + | ||
| 47-54 -- SHA256 of RSA public key for secure-boot + | ||
| 55 -- secure-boot flags (reserved for use by the bootloader) + | ||
| 56-63 -- 256bit device specific private key + |
There was a problem hiding this comment.
Minor quibble, but IMHO 256bit should be 256-bit. And perhaps a hyphen between 'device' and 'specific' ?
There was a problem hiding this comment.
Not sure it matters. Would be better to publish now since the code is out there but feel free to edit directly
lurch
reviewed
Oct 26, 2022
| ---- | ||
|
|
||
| This operation is unlikely to be useful for the vast majority of users, and is irreversible. | ||
|
|
||
| === Device specific private key | ||
| Eight rows of OTP (256bits) are available for use as a device-specific private key. This is intended to support file-system encryption. |
There was a problem hiding this comment.
Space between '256' and 'bits' please
|
Okay, lets merge. |
lurch
added a commit
that referenced
this pull request
Oct 28, 2022
* Tidy up hyphenation around 'bit', following on from comments in #2672 * 64-bit kernel is no longer beta
lurch
added a commit
that referenced
this pull request
Oct 28, 2022
* Tidy up hyphenation around 'bit', following on from comments in #2672 * 64-bit kernel is no longer beta
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.