systemd-boot-random-seed.service - Refresh boot loader random seed at boot
systemd-boot-random-seed.service is a system service that automatically refreshes the boot loader random seed stored in the EFI System Partition (ESP), from the Linux kernel entropy pool. The boot loader random seed is primarily consumed and updated by systemd-boot(7) from the UEFI environment (or systemd-stub(7) if the former is not used, but the latter is), and passed as initial RNG seed to the OS. It is an effective way to ensure the OS comes up with a random pool that is fully initialized.
The service also automatically generates a 'system token' to store in an EFI variable in the system's NVRAM. The boot loader may then combine the on-disk random seed and the system token by cryptographic hashing, and pass it to the OS it boots as initialization seed for its entropy pool. Note: the random seed stored in the ESP is refreshed on every reboot ensuring that multiple subsequent boots will boot with different seeds. On the other hand, the system token is generated randomly once, and then persistently stored in the system's EFI variable storage, ensuring the same disk image won't result in the same series of boot loader seed values if used on multiple systems in parallel.
The systemd-boot-random-seed.service unit invokes the bootctl random-seed command, which updates the random seed in the ESP, and initializes the system token if it's not initialized yet. The service is conditionalized so that it is run only when a boot loader is used that implements the Boot Loader Interface.
For further details see bootctl(1), regarding the command this service invokes.
Note the relationship between systemd-boot-random-seed.service and systemd-random-seed(8). The former maintains the random seed consumed and updated by the boot environment (i.e. by systemd-boot(7) or systemd-stub(7)), the latter maintains a random seed consumed and updated by the OS itself. The former ensures that the OS has a filled entropy pool already during earliest boot when regular disk access is not available yet (i.e. when the OS random seed cannot be loaded yet). The latter is processed much later, once writable disk access is available. Thus it cannot be used to seed the initial boot phase, but typically has much higher quality of entropy. Both files are consumed and updated at boot, but at different times. Specifically:
This logic should ensure that the kernel's entropy pool is seeded during earliest bool already, if possible, but the highest quality entropy is propagated back to both on-disk seeds.
- Boot Loader Interface