I have a report of the RC2 ISO image at http://ftp.fortunaty.net/DragonFlyBSD/iso-images/dfly-1.0RC2.iso.gz having the wrong MD5 checksum; double-check when downloading. You should get:
MD5 (dfly-1.0RC2.iso.gz) = 9b39227698a0b7a4d4f3d18f7ad6ff75
I have a report of the RC2 ISO image at http://ftp.fortunaty.net/DragonFlyBSD/iso-images/dfly-1.0RC2.iso.gz having the wrong MD5 checksum; double-check when downloading. You should get:
MD5 (dfly-1.0RC2.iso.gz) = 9b39227698a0b7a4d4f3d18f7ad6ff75
Comments are closed.
So you’re saying it’s a bad thing that running md5 on my image returned the following:
f3789b3c1be47758203f9e8a4d8c6a2a
;^)
Anyone keeping a regular mtree?
For that matter, anyone have thoughts or tips on best-practices for keeping a mtree on WORM? (I remember thinking about this, or eavesdropping on OpenBSD traffic about it, and realizing you sort of want an extra box, if paranoid of compromised clocks. Anyone want to build an ‘integrity appliance’ with GPS timekeeping? I’ll make the coffee and vacuum the office.. ;))