Creating image for INTERMEDIATE
Installing dependencies
Detected Package Manager: apt
Detected Distro: Debian
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libfaketime
The following NEW packages will be installed:
faketime libfaketime sbsigntool
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 133 kB of archives.
After this operation, 617 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://debian-archive.trafficmanager.net/debian bookworm/main amd64 libfaketime amd64 0.9.10-2.1 [47.3 kB]
Get:2 http://debian-archive.trafficmanager.net/debian bookworm/main amd64 faketime amd64 0.9.10-2.1 [17.6 kB]
Get:3 http://debian-archive.trafficmanager.net/debian bookworm/main amd64 sbsigntool amd64 0.9.4-3.1 [68.4 kB]
Fetched 133 kB in 0s (436 kB/s)
Selecting previously unselected package libfaketime:amd64.
(Reading database ... 46719 files and directories currently installed.)
Preparing to unpack .../libfaketime_0.9.10-2.1_amd64.deb ...
Unpacking libfaketime:amd64 (0.9.10-2.1) ...
Selecting previously unselected package faketime.
Preparing to unpack .../faketime_0.9.10-2.1_amd64.deb ...
Unpacking faketime (0.9.10-2.1) ...
Selecting previously unselected package sbsigntool.
Preparing to unpack .../sbsigntool_0.9.4-3.1_amd64.deb ...
Unpacking sbsigntool (0.9.4-3.1) ...
Setting up sbsigntool (0.9.4-3.1) ...
Setting up libfaketime:amd64 (0.9.10-2.1) ...
Setting up faketime (0.9.10-2.1) ...
Processing triggers for man-db (2.11.2-2) ...
Cannot assign label: INTERMED : (127)
Device
APU2
RTE version
1.1.0
Affected component(s) or functionality
No response
Brief summary
Cannot assign label: INTERMED : (127) when generating VBOOT key
How reproducible
No response
How to reproduce
debian@debian:~/open-source-firmware-validation/scripts/secure-boot/generate-images$ ./sb-img-wrapper.sh
Expected behavior
Key should be generated.
Actual behavior
Link to screenshots or logs
There are no logs.
Additional context
No response
Solutions you've tried
No response