Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

secvarctl-0.3-150400.1.5 RPM for ppc64le

From OpenSuSE Leap 15.5 for ppc64le

Name: secvarctl Distribution: SUSE Linux Enterprise 15
Version: 0.3 Vendor: SUSE LLC <https://www.suse.com/>
Release: 150400.1.5 Build date: Sat May 7 23:19:38 2022
Group: Unspecified Build host: ibs-power9-10
Size: 167528 Source RPM: secvarctl-0.3-150400.1.5.src.rpm
Packager: https://www.suse.com/
Url: https://github.com/open-power/secvarctl
Summary: Suite of tools to manipulate and generate Secure Boot variables on POWER
The purpose of this tool is to simplify and automate the process of reading and writing secure boot keys.
secvarctl allows the user to communicate, via terminal commands, with the keys efficiently.

Secure Variables are responsible for loading the target OS/hypervisor during Secure Boot. There are currently four secure variables in the Secure Boot process: The Platform Key (PK), Key Exchange Key (KEK), Database Key (db) and Blocklist Key (dbx).The PK serves as the root key, usually supplied by platform owner, if there is no PK then Secure Boot is not enabled. The PK has authority over all other keys. The KEK is usually provided by the OS vendor and has authority over the db and dbx. The db has authority over the kernels and other user specific firmware. The dbx has authority over kernels and specific firmware that are not to be loaded.

Updating of these secure variables requires a specific format for success. If updating the PK, KEK or db, an x509 public key must be contained in an EFI Signature List (ESL). If updating the dbx, the binary that is to be banned must be hashed and placed in an ESL. Then, a PKCS7 structure must be generated by signing the new ESL with the private key of a secure variable that has authority over the variable being updated (Example: if updating the db, the new ESL must be signed by either the KEK or PK). Finally, the new ESL must be appended to the generated PKCS7 and the whole structure is then placed into what is called an Auth file (this adds extra header information, timestamp and content size). When the Auth file is generated, the resulting file is ready to be submited. Once submitted, the update is only applied when the POWER machine is rebooted.

Provides

Requires

License

Apache-2.0

Changelog

* Thu Sep 23 2021 msuchanek@suse.com
  - Version 0.2+git31 released as 0.3 (jsc#SLE-18126).
* Mon Sep 20 2021 msuchanek@suse.com
  - Update to version 0.2+git31~26ea751:
  - Remove workaround for wrong man page location - fixed upstream.
* Wed Jun 16 2021 msuchanek@suse.com
  - Initial packaging (jsc#SLE-18126).

Files

/usr/bin/secvarctl
/usr/share/doc/packages/secvarctl
/usr/share/doc/packages/secvarctl/README.md
/usr/share/licenses/secvarctl
/usr/share/licenses/secvarctl/LICENSE
/usr/share/man/man1/secvarctl.1.gz


Generated by rpm2html 1.8.1

Fabrice Bellet, Tue Apr 9 19:50:46 2024