What are the performance differences between SHA-256 and 512? What throughput can you expect when checking hashes? And how to correct errors detected?
Since November 2020, every T2 and Apple silicon Mac that has booted Big Sur or later in Full Security mode has check the integrity of its 9 GB SSV.
From its outset, APFS hasn’t tested the integrity of file data stored on it. Would this be a good idea, or should macOS switch to the ZFS file system instead?
APFS has no feature to check file data integrity. Dintch and Fintch are two apps that tag files with SHA-256 hashes to address this. New versions.
How to do this using macOS and free tools. Introduces a new version of Dintch which lets you control its speed, particularly on Apple silicon.
Storage has to be reliable, efficient and resilient. However, efficiency and resilience oppose one another. What’s the best solution? New file formats, CRC in the file system, or what?
App signatures are about more than just the certificate. That provides a chain of trust going back to Apple, and supports integrity checks and entitlements.
There have been changes to the way that macOS 12 checks executable code when asked to run it. Summarised in a diagram.
For many users, it’s essential to be able to check the integrity of the data which are in a backup. This feature has changed when backing up to APFS.
What are checksums, CRCs and hashes? What is required for a hash to be cryptographic, and how any of these affect your Mac? Some answers and explanations.