Package Details: chkboot 1.3-1

Git Clone URL: https://aur.archlinux.org/chkboot.git (read-only)
Package Base: chkboot
Description: Create hashes of all files under /boot and warns the user if they are modified
Upstream URL: https://github.com/grazzolini/chkboot
Keywords: boot check security
Licenses: GPL
Submitter: None
Maintainer: grazzolini
Last Packager: grazzolini
Votes: 13
Popularity: 0.001218
First Submitted: 2012-02-23 08:55
Last Updated: 2019-04-16 21:41

Dependencies (4)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

grazzolini commented on 2019-09-14 04:19

@pancakes,

This seems to be used by systemd-boot, see https://systemd.io/RANDOM_SEEDS. Looks like if you have a seed on the efivar, it'll merge that with the file, triggering chkboot on every boot. My suggestion would be to not mount the ESP under the same path as your /boot partition. If you mount your ESP to /boot/efi, try mounting it to /efi.

pancakes commented on 2019-09-12 08:57

I recently started getting a new /boot/loader/random-seed file on boot on every reboot, triggering chbkoot's warnings. Anyone has an idea on what's the cause behind this? I suspect a systemd update, in which case, is it happening to others as well?

DefaultSpatula commented on 2019-04-16 22:11

I appreciate you taking the time to update this package; thanks!

Notice to everyone: After updating to 1.3, chkboot will warn you about changed hashes. This is because the hashing algorithm has been updated to use SHA512.

grazzolini commented on 2019-04-15 16:51

@DefaultSpatula

I'm going through your PR's. But please, don't advise anyone on using then, specially the EFI one.

DefaultSpatula commented on 2019-04-13 15:05

A heads up for anyone trying to use this on an EFI system: Manually apply pull requests #9, #10, and #11 from github and it'll work perfectly.

Additionally, pull request #13 includes pacman hooks to automate the process when your boot images, systemd, or kernel microcode receive updates.

grazzolini commented on 2015-08-17 15:02

@noxp
You're right, this hook has some limitations, specially regarding the usage of a EFI system partition as /boot. I am currently planning a complete revamp of this hook, including a merge with https://aur.archlinux.org/packages/mkinitcpio-chkcryptoboot/

It shouldn't be difficult to add a special case for an EFI system partition, since the UEFI specification determines it must be a FAT filesystem. As for the disk head, it backups the MBR, which on GPT is the protective MBR. Unless you are creating your GPT without it. Right now it backups 512 bytes. But that also backups the partition table, on a MBR disk. If you change your partitioning, it would trigger a false positive chkboot warning.

noxpo commented on 2015-08-16 08:25

Thx for your great work man. My /boot is a FAT32 UEFI System partition on a disk with a GPT label. For this case, I have two suggestions:

1) The number of sectors of the stored disk head should be configurable, I use 34 to cover the entire GPT.

2) The inode and extent fileds in the boot file list don't make a lot of sense for a FAT filesystem, how about comparing the first x sectors of the partiton head holding the file allocation table?

grazzolini commented on 2015-05-04 04:38

@pezz
Expect it to be updated today, at most tomorrow. I still haven't fixed all the bugs chkboot-git had.

pezz commented on 2015-05-03 23:33

Would have been nice to have this updated before deleting chkboot-git.

pezz commented on 2014-02-07 00:29

This is great, nice work!