README: Add description of automated process #16
Conversation
This file contains 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
README.md
Outdated
|
|
||
| The chain of trust can be verified with multiple steps. The sha256 of the tarball can be compared | ||
| with the listed sha256. The timestamps of the tarball and sha256 file can be compared. The build | ||
| log can be compared with the sumnary.csv that is included in the tarball to verify the buildroot |
There was a problem hiding this comment.
sumnary -> summary.csv
Update to add description of automated process as a proof of trust for the toolchains hosted by Bootlin. Signed-off-by: Jared Bents <[email protected]>
jmbents
force-pushed
the
readme-build-process
branch
from
1fdb43d to
8f0f60b
Compare
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.
Update to add description of automated process as a proof of trust
for the toolchains hosted by Bootlin.
Signed-off-by: Jared Bents [email protected]
This may not be the proper place for this information as perhaps the About page on Bootlin is better suited. After switching to the Bootlin toolchains for a project, we worked with our security team to come up with a story on why the Bootlin toolchains can be trusted since we were no longer building the toolchain from source. Upstreaming with a more general description than what we documented for the toolchains we are using to share for others. Please add any corrections to the process or further clarification that is wanted as comments.