Package Details: secureboot-helper 1.2.0-1

Git Clone URL: https://aur.archlinux.org/secureboot-helper.git (read-only, click to copy)
Package Base: secureboot-helper
Description: Kernel signing helper for UEFI secure boot
Upstream URL: https://wiki.archlinux.org/index.php/Secure_Boot#Signing_kernel_with_pacman_hook
Licenses: GPL
Conflicts: sbupdate
Submitter: brli
Maintainer: brli
Last Packager: brli
Votes: 2
Popularity: 0.000000
First Submitted: 2019-08-02 18:37 (UTC)
Last Updated: 2024-04-23 01:00 (UTC)

Pinned Comments

brli commented on 2019-08-02 18:45 (UTC) (edited on 2019-08-02 18:46 (UTC) by brli)

Please note that you should also move the signatures to your ESP where it should be formated FAT32, and insert the keys from your firmware interface the first time the sigs are generated, and you should remove them from there after successfully boot from secure boot.

Read the manuals of the manufacturer of board or laptop for further information.

Latest Comments

SolarAquarion commented on 2024-04-21 04:50 (UTC)

==> Starting prepare()... /home/solaraquarion/build/secureboot-helper/PKGBUILD: line 59: !: command not found ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... ==> Generating PK.key .+......+......+.....+...+...............+.......+.....+.........+...+...+...+....+++++++++++++++++++++++++++++++++++++++.+.......+..+.+.........+...+......+.....+.+...........+...+................+.....+...+.+..+++++++++++++++++++++++++++++++++++++++.....+..+......+..........+..+..................+.......+........+....+..+...+...+....+.....+....+......+........+...+....+.........+.....+..........+......+...+........+....+...........+...+......+......+....+.........+............+............+..+...+.+..............+............++++++ ........+..+............+...+......+.+...+...+..+.+......+...+............+...........+..........+.....+++++++++++++++++++++++++++++++++++++++..+.+............+.....+...+....+...+.....+...+.......+...+..+...+.........+.+......+...+..+++++++++++++++++++++++++++++++++++++++...............+..+.+..+.+..+.........+....+......+......+........+.+.....+....+............+..+.+.....+.+.....+.+.....+.......+...+.....+.........+.+.........+...+......+..+...+.+.........+..+...+....+.....+.+...........+.........+.........+...+...............+...+......+....+......+...+..+......+...+....+...+..+......+..........+...............+..+...+.+...+........+..........+........+.......+..+.+.........+......+..+....+........+............+.+..+.+...........+...+...+.........+.+..++++++

Timestamp is 2024-4-21 00:49:40 Authentication Payload size 901 Signature of size 1223 Signature at: 40 Timestamp is 2024-4-21 00:49:40 Authentication Payload size 40 Signature of size 1223 Signature at: 40 ==> Generating KEK.key .+++++++++++++++++++++++++++++++++++++++...+..+....+...+......+..+.......+...........+......+.+..+......+.........+.............+..+......+.+...+..+.....................+....+........+.+............+..+.+.....+.......+..+.......+++++++++++++++++++++++++++++++++++++++.........+..+................+..+...+....+...+.....+......+............+...+....+......+.....+.........+......+.+...+...+..+...+...+.+.........+...........+.+.....++++++ .....+...+...+......+.+...+.........+...............+++++++++++++++++++++++++++++++++++++++...+....+............+......+............+...+.....+....+...+.....+...+...+.........+.+......+...+....................+.......+.....+...+...+.......+........+.......+..+...+.+..+++++++++++++++++++++++++++++++++++++++.+......+........+.+..+...+..........+............+...+......+...+...........+......+.++++++

/home/solaraquarion/build/secureboot-helper/PKGBUILD: line 83: GUID.txt: No such file or directory

brli commented on 2019-08-02 18:45 (UTC) (edited on 2019-08-02 18:46 (UTC) by brli)

Please note that you should also move the signatures to your ESP where it should be formated FAT32, and insert the keys from your firmware interface the first time the sigs are generated, and you should remove them from there after successfully boot from secure boot.

Read the manuals of the manufacturer of board or laptop for further information.