7 Commits

Author SHA1 Message Date
Bejean Mosher
d6fdbca903 fix: Remove deprecated python imp module
Python imp module is removed in 3.12+ and will cause a build error.
Replace with importlib.machinery.SourceFileLoader.

Signed-off-by: Bejean Mosher <bejean.mosher@intel.com>
2024-06-17 08:11:02 -07:00
Guo Dong
16d7d22040 Update BtgSign tool
Currently StitchLoader.py is under platform package, and
the common tool BtgSign.py should not depend on that tool.
And BtgSign.py indeed doesn't depend on it, so just update
it to make it could work without StitchLoader.py.

Signed-off-by: Guo Dong <guo.dong@intel.com>
2021-12-16 08:11:53 -07:00
Mike Crowe
990e3e81e6 Use LF line endings in the repository
Convert the line endings stored for all text files in the repository to
LF. The majority previously used DOS-style CRLF line endings. Add a
.gitattributes file to enforce this and treat certain extensions as
never being text files.

Update PatchCheck.py to insist on LF line endings rather than CRLF.
However, its other checks fail on this commit due to lots of
pre-existing complaints that it only notices because the line endings
have changed.

Silicon/QemuSocPkg/FspBin/Patches/0001-Build-QEMU-FSP-2.0-binaries.patch
needs to be treated as binary since it contains a mixture of line
endings.

This change has implications depending on the client platform you are
using the repository from:

* Windows

The usual configuration for Git on Windows means that text files will
be checked out to the work tree with DOS-style CRLF line endings. If
that's not the case then you can configure Git to do so for the entire
machine with:

 git config --global core.autocrlf true

or for just the repository with:

 git config core.autocrlf true

Line endings will be normalised to LF when they are committed to the
repository. If you commit a text file with only LF line endings then it
will be converted to CRLF line endings in your work tree.

* Linux, MacOS and other Unices

The usual configuration for Git on such platforms is to check files out
of the repository with LF line endings. This is probably the right thing
for you. In the unlikely even that you are using Git on Unix but editing
or compiling on Windows for some reason then you may need to tweak your
configuration to force the use of CRLF line endings as described above.

* General

For more information see
https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings .

Fixes: https://github.com/slimbootloader/slimbootloader/issues/1400
Signed-off-by: Mike Crowe <mac@mcrowe.com>
2021-11-10 12:46:42 -08:00
Raghava Gudla
878190fadf Enable Oem key has generation for Btg0 profile (#1279)
Latest BpmGen2 require Oem Key hash generation for
Btg legacy profile also. This patch enabled oem key generation
for Btg0 profile.

Signed-off-by: Raghava Gudla <raghava.gudla@intel.com>
2021-08-31 10:54:42 -07:00
James Gutbub
ea1cd3f0ac Remove trailing space from OemPublicKeyHash field (#1274)
When boot guard profile is non-zero the OemPublicKeyHash
will be populated in the stitching XML file but FIT/mFIT
is giving a warning message:

OemPublicKeyHash. Exception: set_value failed.

This will remove the trailing space added to the last byte
given in the OemPublicKeyHash and resolve the warning.

Signed-off-by: James Gutbub <james.gutbub@intel.com>
2021-08-25 15:37:35 -07:00
Subash Lakkimsetti
c14cdfdba5 Update path for oem key manifets
Some platforms FIT tool do not detect sourceDir.
Change to absoulte path.

Signed-off-by: Subash Lakkimsetti <subash.lakkimsetti@intel.com>
2021-03-22 21:20:10 -07:00
Subash Lakkimsetti
21b73a70c6 Common boot guard signing as seperate and standalone script
This patch adapts common btg utility and restructures
stitch script and separates security functionality.

BtgSign.py - Common Boot guard signing and oem key manifest generation.
			 It also supports signing in standalone mode. Stanalone mode can
			 be used sign bootloader bin and stitch using FIT tool.

security_stitch_help.py - Interface functionality for Btg manifest and
			 update xml with security updates. This is as per the client
			 platform FIT xml format.

Signed-off-by: Subash Lakkimsetti <subash.lakkimsetti@intel.com>
2021-03-19 22:19:07 -07:00