To check the integrity of important documents, we’re going to calculate their SHA256 digests. But where should those be stored if HFS+ and APFS don’t have a suitable attribute?
If macOS can’t do it, how should we check the integrity of important files? Use a checksum, or a hash function? And which?
We take for granted that our files remain uncorrupted, but know that isn’t always true. How can we fix or even detect such changes?
First release version, for El Capitan to Catalina. And completely free of course.
Other major changes include detailed reporting, and user control over the size of buffer used, bringing big performance improvements.
How can you tell whether the file you see in storage today is the same as it was a year ago when you last opened it?
Over time, stored data gets gradually corrupted. But over what period – months, years or centuries? And at what rate?
Now is a good time to re-evaluate which version of macOS your Macs are running. In the next […]
The fine line between precision and obscurity examined in the Finder, against Apple’s Style Guide, and its accuracy. And what does HD stand for?
Why is Apple soldering in the SSDs of so many new Macs? What problems does it produce, and should you avoid them?