Date: Mon, 1 Mar 2021 15:38:58 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd@dreamchaser.org, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: installed ports library audit? Message-ID: <0935eab6-d458-2c3e-3f8a-a6879fe27363@FreeBSD.org> In-Reply-To: <97db8511-c5e0-26cc-5e56-4dfa976d7d12@FreeBSD.org> References: <a99e82cc-da39-70e8-f3b1-7b250250876a@dreamchaser.org> <97db8511-c5e0-26cc-5e56-4dfa976d7d12@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/03/2021 15:36, Matthew Seaman wrote: > On 01/03/2021 03:43, Gary Aitken wrote: >> I just mostly recovered from a system crash where /usr was corrupted and >> had to be recovered using fsck; couldn't completely recover using the >> journal. >> >> I suspect the trashed files are in one of a few libraries. I'm wondering >> if there's an easy way to audit all files installed by given ports, >> i.e. do an sha256 or something like that on each and compare with the >> known >> good if it's available somewhere? > > pkg-check(8) -- specifically `pkg check -r -x .` will show you any file > known to pkg(8) where the on-disk copy doesn't match the checksum in the > pkgdb. Dammit. `pkg check -s -x .` `-r` is exactly what you don't want, as that will make pkg(8) believe the corrupted files are actually correct. Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0935eab6-d458-2c3e-3f8a-a6879fe27363>