Audit your /boot files with md5deep audit tool

Take the media device that you wrote (with the dd command) the image file fore Raspberry Pi.   Plug that media device (into your development workstation computer)    Make some mount points with 'mkdir' command.  Your setup and O/S might automatically make the mount points and mount the device for you.

sudo mkdir /media/da1s1

sudo mkdir /media/da1s2a

mount -t msdos /dev/mmcsda1s1  /media/da1s1

mount -t ufs /dev/mmcsda1s2a  /media/da1s2a

 

Here is the manual page for md5deep

 http://md5deep.sourceforge.net/md5deep.html

http://md5deep.sourceforge.net/start-md5deep.html 

https://en.wikipedia.org/wiki/Md5deep 

https://serverfault.com/questions/390522/how-can-i-easily-confirm-in-linux-that-two-separate-directories-have-the-exact-s 

 

While you could hack together a quick script that will calculate individual MD5 hashes for individual files in a directory, the better way to do it would be to use a tool called md5deep which will recursively calculate the hashes of all files in a directory, and then output them to a file. It can then be used on another directory, taking the first hash file as an input, and providing you with a list of files that are different between the two directories.

So, taking your example, you would follow this process:

1. Calculate hashes of the required directory on Server A:

   md5deep -r /opt/foo/ > file_hashes.txt

2. Copy the file file_hashes.txt file onto Server B for comparison.

3. Calculate hashes of the required directory on Server B, but taking the file hashes from Server A as an input file by using the -x flag to only show files that are different:

   md5deep -x file_hashes.txt -r /opt/foo/

The md5deep set of tools forms part of the package management system of most distros, and the great thing is that it supports a number of different hashing algorithms, not just MD5. So if you're paranoid about collisions, you have a number of alternatives available. The following tools form part of md5deep, each providing an alternative hashing algorithm:

   md5deep - Compute and compare MD5 message digests
   sha1deep - Compute and compare SHA-1 message digests
   sha256deep - Compute and compare SHA-256 message digests
   tigerdeep - Compute and compare Tiger message digests
   whirlpooldeep - Compute and compare Whirlpool message digests

 

Github location for HASHDEEP/md5deep tools.  Read for information

https://github.com/jessek/hashdeep   

from Jesse Kornblum Github

 

 

hope@localhost ~> pwd
/home/hope

hope@localhost ~> cd /media/da1s1
hope@localhost /m/da1s1> ls
EFI bootcode.bin fixup_db.dat start_cd.elf
README config.txt fixup_x.dat start_db.elf
armstub8.bin fixup.dat overlays start_x.elf
bcm2710-rpi-3-b.dtb fixup_cd.dat start.elf u-boot.bin
hope@localhost /m/da1s1> ls -l
total 25248
drwxrwxr-x 1 root wheel 4096 May 10 09:38 EFI
-rw-r--r-- 1 root wheel 124 May 10 09:38 README
-rw-r--r-- 1 root wheel 5888 May 10 09:38 armstub8.bin
-rw-r--r-- 1 root wheel 28392 May 10 09:38 bcm2710-rpi-3-b.dtb
-rw-r--r-- 1 root wheel 52456 May 10 09:38 bootcode.bin
-rw-r--r-- 1 root wheel 141 May 10 09:38 config.txt
-rw-r--r-- 1 root wheel 7314 May 10 09:38 fixup.dat
-rw-r--r-- 1 root wheel 3187 May 10 09:38 fixup_cd.dat
-rw-r--r-- 1 root wheel 10298 May 10 09:38 fixup_db.dat
-rw-r--r-- 1 root wheel 10298 May 10 09:38 fixup_x.dat
drwxrwxr-x 1 root wheel 20480 May 10 09:38 overlays
-rw-r--r-- 1 root wheel 2952960 May 10 09:38 start.elf
-rw-r--r-- 1 root wheel 793116 May 10 09:38 start_cd.elf
-rw-r--r-- 1 root wheel 4794472 May 10 09:38 start_db.elf
-rw-r--r-- 1 root wheel 3704808 May 10 09:38 start_x.elf
-rw-r--r-- 1 root wheel 513168 May 10 09:38 u-boot.bin
hope@localhost /m/da1s1>

hope@localhost /m/da1s1> pwd
/media/da1s1
hope@localhost /m/da1s1> ls
EFI bootcode.bin fixup_db.dat start_cd.elf
README config.txt fixup_x.dat start_db.elf
armstub8.bin fixup.dat overlays start_x.elf
bcm2710-rpi-3-b.dtb fixup_cd.dat start.elf u-boot.bin
hope@localhost /m/da1s1> md5deep -z -b * > ~/audit_bootfiles_raspi4b_may12.md5
/media/da1s1/EFI: Is a directory
/media/da1s1/overlays: Is a directory
hope@localhost /m/da1s1> ls ~/audit_bootfiles_raspi4b_may12.md5
/home/hope/audit_bootfiles_raspi4b_may12.md5
hope@localhost /m/da1s1> ls -l ~/audit_bootfiles_raspi4b_may12.md5
-rw-r--r-- 1 hope wheel 815 May 12 02:03 /home/hope/audit_bootfiles_raspi4b_may12.md5
hope@localhost /m/da1s1> cat ~/audit_bootfiles_raspi4b_may12.md5
5888 74647627f798ca2a3fbed3c13e342c71 armstub8.bin
141 daa84f7928905470af6969db30de4af3 config.txt
3187 3af5097c49ce34ba375452ff5e486c05 fixup_cd.dat
28392 1a08a1b0a13ae93e0106384057136be3 bcm2710-rpi-3-b.dtb
52456 bc175da040361a117dea6ca0d5459c12 bootcode.bin
124 5aeff4c2e6496760c2b754cf51fabf6e README
7314 81f4693f6e65112b4e545d3f02f018f0 fixup.dat
10298 6bebd59753c504c3b312371014d8df26 fixup_db.dat
10298 4f30700929f834278238b1b0b6327b93 fixup_x.dat
793116 75c18a9fb7a5a851f4ee87bb70673b40 start_cd.elf
513168 e42c9fa7253d4c8d30c3c3e1c88f328e u-boot.bin
2952960 1ac5026674c8b8c9acdd8e43e7bc1d81 start.elf
3704808 40810618fd52598375c18856db1f13f9 start_x.elf
4794472 cb35a8bed01f9b4bb9b80105b2a1dc8a start_db.elf
hope@localhost /m/da1s1>



md5deep -h
md5deep version 4.4 by Jesse Kornblum and Simson Garfinkel.
$ md5deep [OPTION]... [FILES]...
See the man page or README.txt file or use -hh for the full list of options
-p <size> - piecewise mode. Files are broken into blocks for hashing
-r - recursive mode. All subdirectories are traversed
-e - show estimated time remaining for each file
-s - silent mode. Suppress all error messages
-z - display file size before hash
-m <file> - enables matching mode. See README/man page
-x <file> - enables negative matching mode. See README/man page
-M and -X are the same as -m and -x but also print hashes of each file
-w - displays which known file generated a match
-n - displays known hashes that did not match any input files
-a and -A add a single hash to the positive or negative matching set
-b - prints only the bare name of files; all path information is omitted
-l - print relative paths for filenames
-t - print GMT timestamp (ctime)
-i/I <size> - only process files smaller/larger than SIZE
-v - display version number and exit
-d - output in DFXML; -u - Escape Unicode; -W FILE - write to FILE.
-j <num> - use num threads (default 4)
-Z - triage mode; -h - help; -hh - full help


md5deep -hh
md5deep version 4.4 by Jesse Kornblum and Simson Garfinkel.
$ md5deep [OPTION]... [FILES]...
See the man page or README.txt file or use -hh for the full list of options
-p <size> - piecewise mode. Files are broken into blocks for hashing
-r - recursive mode. All subdirectories are traversed
-e - show estimated time remaining for each file
-s - silent mode. Suppress all error messages
-z - display file size before hash
-m <file> - enables matching mode. See README/man page
-x <file> - enables negative matching mode. See README/man page
-M and -X are the same as -m and -x but also print hashes of each file
-w - displays which known file generated a match
-n - displays known hashes that did not match any input files
-a and -A add a single hash to the positive or negative matching set
-b - prints only the bare name of files; all path information is omitted
-l - print relative paths for filenames
-t - print GMT timestamp (ctime)
-i/I <size> - only process files smaller/larger than SIZE
-v - display version number and exit
-d - output in DFXML; -u - Escape Unicode; -W FILE - write to FILE.
-j <num> - use num threads (default 4)
-Z - triage mode; -h - help; -hh - full help
-S - Silent mode, but warn on bad hashes
-0 - use a NUL (\0) for newline.
-k - print asterisk before filename
-u - escape Unicode characters in filenames
-B - verbose mode; repeat for more verbosity
-C - OS X only --- use Common Crypto hash functions
-Fb - I/O mode buffered; -Fu unbuffered; -Fm memory-mapped
-f <file> - take list of files to hash from filename
-o[bcpflsde] - expert mode. Only process certain types of files:
b=block dev; c=character dev; p=named pipe
f=regular file; l=symlink; s=socket; d=door e=Windows PE
-D <num> - set debug level to nn
hope@localhost /m/da1s1>

 

So, now you have tools to  categorize and qualify the files in the /boot directory.  Use an image that you have tested to boot up and work on your hardware with your HDMI monitor or display.

Run  the md5deep command tool to create a file that has size and md5 sums inside for the msdos FAT32 /boot directory .  Use this hash file to compare with new versions of the raspberry pi FreeBSD boot image with the /boot directory.

Here is a initial command line to use. Modify for your needs.

md5deep -z -b * > ~/audit_bootfiles_raspi4b_may12.md5_hash

Great resource that has examples of using md5deep near the end.

https://unix.stackexchange.com/questions/22730/is-there-md5-or-similar-to-a-folder-how-to-verify-if-two-folders-are-equal