OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel low very-common DISPUTE

bootctl warns 'random seed file is world accessible, which is a security hole'

archendeavouroscachyosmanjarosystemd-bootuefi
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

bbs 287695 has both warning lines (with /efi), notes that the system boots, and fixes it by changing fstab from 0022 to fmask=0077,dmask=0077. The strings in systemd 261.2's bootctl and libsystemd-shared match both messages. bootctl(8) says random-seed generates or refreshes the seed on the ESP for systemd-boot. On this machine /proc/mounts shows /boot as vfat with fmask=0077,dmask=0077, and grub and systemd-boot are not in use, which confirms the Omarchy note. Two defects. First, the cause says bootctl 'refuses to treat' a readable seed as secret. bootctl prints a warning and carries on, as the reporter's working install shows. Second, the cited EFI system partition wiki page says nothing about the random seed or the warning. Its only fmask/dmask lines are for a bind-mount setup. It is replaced by the Fstab page, whose ESP examples use fmask=0177,dmask=0077, and the FAT page, which states FAT has no Linux permissions. Not exercised: /boot was not remounted and bootctl was not run.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.
RISK

A typo in the /boot fstab line can drop the next boot to emergency mode. Run sudo findmnt --verify before rebooting.

Symptom

Running bootctl install or bootctl update, or watching the systemd-boot update service, prints:


Mount point '/boot' which backs the random seed file is world accessible, which is a security hole!
Random seed file '/boot/loader/random-seed' is world accessible, which is a security hole!

(or /efi in place of /boot). The system boots fine.

Cause

The ESP is a FAT filesystem with no Unix permissions. Ownership and modes come from the fmask and dmask mount options, and fstab lines written by genfstab or older installers often carry fmask=0022,dmask=0022, which makes every file readable by all users. systemd-boot keeps a random seed on the ESP for early-boot entropy. When bootctl writes or refreshes that seed and finds it, or the mount point backing it, readable by other users, it prints the warning and carries on. The seed is still written and the system still boots. Any local user could read it until the masks are tightened.

Fix

Tighten the ESP mount options in /etc/fstab. Change fmask=0022,dmask=0022 to:


UUID=XXXX-XXXX  /boot  vfat  rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro  0 2

Keep your own UUID and mount point. Then remount and regenerate the seed:


sudo systemctl daemon-reload
sudo umount /boot && sudo mount /boot
sudo bootctl random-seed

Omarchy 4 already mounts its ESP with fmask=0077,dmask=0077, and uses Limine rather than systemd-boot, so it does not see this warning.

Verify

findmnt -n -o OPTIONS /boot shows fmask=0077,dmask=0077, and sudo bootctl random-seed completes with no 'world accessible' warning.

Sources

bootctl-random-seed-world-accessible