[secure boot]Add Secure Boot Feature #3
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
davidpil2002
force-pushed
the
secure_boot_support
branch
5 times, most recently
from
726e5ff
to
944ac0a
Compare
davidpil2002
force-pushed
the
secure_boot_support
branch
from
767ca97
to
b8ac9fc
Compare
davidpil2002
force-pushed
the
secure_boot_support
branch
from
878e879
to
46b3040
Compare
davidpil2002
force-pushed
the
secure_boot_support
branch
from
03f3cf5
to
62092f4
Compare
davidpil2002
force-pushed
the
secure_boot_support
branch
2 times, most recently
from
d9d52a2
to
9cc6b60
Compare
davidpil2002
force-pushed
the
secure_boot_support
branch
3 times, most recently
from
fde9898
to
c758293
Compare
… sonic fs (like original grub.cfg)instead in boot directory
Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
… fix variable typo SECURE_UPGRADE_PROD_SIGNING_TOOL_DST instead SECURE_UPGRADE_PROD_SIGNING_TOOL_SOURCE
davidpil2002
force-pushed
the
secure_boot_support
branch
from
ee7384f
to
7509fc5
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.
Why I did it
Add Secure Boot support to SONiC OS.
Secure Boot (SB) is a verification mechanism for ensuring that code launched by a computer's UEFI firmware is trusted. It is designed to protect a system against malicious code being loaded and executed early in the boot process before the operating system has been loaded.
How I did it
Added a signing process to sign the following components:
shim, grub, Linux kernel, and kernel modules when doing the build, and when feature is enabled in build time according to the HLD explanations (the feature is disabled by default).
How to verify it
There are self-verifications of each boot component when building the image, in addition, added an end-to-end test in sonic-mgmt repo that checks that the boot succeeds when loading a secure system.
TBD: PR link of sonic-mgmt will be added soon
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
No REDIS DB used in this feature
HLD link: sonic-net/SONiC#1028
A picture of a cute animal (not mandatory but encouraged)