affcompare(1)

✨ affcompare(1) β€” NAME ✨

okay bestie, let's get into it πŸ’…πŸ¦‹ this is the affcompare manual page, which is the "compare the contents of an ISO file to an AFF file" tool. it's giving forensics-core energy, no cap πŸ”

🌸 NAME 🌸

affcompare β€” compare the contents of an ISO file to an AFF file πŸ’–

🧚 SYNOPSIS 🧚

affcompare [options] file1 file2
affcompare [options] -r dir1 dir2
affcompare [options] -s file1 file2...

πŸ’… DESCRIPTION πŸ’…

okay so this tool compares the contents of an ISO file to an AFF file ✨ and if they match? it can optionally delete the ISO file 😭 so be careful, bestie, that part is serious πŸ’€

it's part of the AFFLIBv3 library, which is what provides AFF πŸŽ€

AFF is an open and extensible file format for storing disk images and their associated metadata 🌈 it's super useful in a bunch of scenarios, like computer forensics investigations πŸ”₯ iykyk

πŸŽ€ OPTIONS πŸŽ€

okay so the options are split into two vibes: fast options (compare segments but not their contents) and other options πŸ¦‹

Fast options (compare segments but not their contents) ⚑

  • -e β€” just reports about existence, use it with -r πŸ‘€
  • -p β€” reports the results of preening 🫧
  • -r, dir1 dir2 β€” recursively compares what's in dir1 with dir2, and reports what's in dir1 that's not in dir2 πŸ—‚οΈ
  • -s β€” checks to see if the named files are on Amazon S3 ☁️

Other options πŸ’œ

  • -a β€” prints what's the same (all) βœ…
  • -b β€” prints the numbers of differing sectors πŸ”’
  • -c β€” prints the contents of differing sectors 🧐
  • -h β€” shows the help page πŸ†˜
  • -m β€” just reports about the data, ignoring metadata πŸ™ˆ
  • -P <n> β€” just examines the differences on page 'n' πŸ“„
  • -q β€” quiet mode, no output except for errors 🀫
  • -V β€” just prints the version number and exits 🏷️
  • -v β€” verbose, shows each file as it gets compared πŸ“£

πŸ“ EXAMPLES πŸ“

okay, examples time, bestie 🫢

Compare file1 with file2:

$ affcompare file1.aff file2.aff

Compare similarly-named files in dir1/ and dir2/:

$ affcompare -r dir1 dir2

Reports if files were successfully copied to Amazon S3, checking only for existence and not reading back the bytes (because all writes to S3 are validated by the MD5 of the object):

$ affcompare -s file1.aff file2.aff file3.aff

Compare f1.aff with dir1/f1.aff and f2.aff with dir2/f2.aff:

$ affcompare f1.aff f2.aff dir1/
note that dir1/ must end with a slash, so don't forget it πŸ™

Compare file.aff and file.img:

$ affcompare -b img file.aff

Compare file1.aff, file1.img, etc.:

$ affcompare -b img file1.aff file2.aff file3.aff

Report AFF files in dir1 but not in dir2:

$ affcompare -re dir1 dir2

Report AFF files in dir1 but not on S3 (low bandwidth):

$ affcompare -rse dir1 s3:///

Report AFF files in dir1 but incomplete on S3 (more bandwidth):

$ affcompare -rs dir1 s3:///

πŸ¦‹ SEE ALSO πŸ¦‹

okay so the related tools are: affcat(1), affconvert(1), affcopy(1), affcrypto(1), affdiskprint(1), affinfo(1), affix(1), affrecover(1), affsegment(1), affsign(1), affstats(1), affuse(1), affverify(1), and affxml(1) πŸ“šβœ¨

πŸ‘‘ AUTHOR πŸ‘‘

the AFFLIB was written by Simson L. Garfinkel <simsong@acm.org> and Basis Technology, Inc. 🌟

this manual page was written by Joao Eriberto Mota Filho <eriberto@debian.org> for the Debian project (but may be used by others) 🫢


bestie, that's the whole affcompare page, version 3.7.4 from Oct 2014 🌈 you're literally going to slay with this info, periodt πŸ’–πŸŽ€

πŸ“¦ where this page comes from