I have a bunch of certificate related things, along with a bunch of secure notes stored in the keychain. These, like previously in System Preferences, don’t show up in the new Passwords app (as tested in iOS).
So before I risk losing all that information by installing Sequoia, I wonder if the KeychainAccess.app is still around, allowing me to access these items.
In case Apple is listening: do NOT remove that app, until all the critical functionality is also in Passwords, or some other app….
The old app is still available as /System/Library/CoreServices/Applications
.
In case Apple is listening
Apple is always listening! *mwaa haa haa*
Seriously though, I see two parts to this:
-
The potential for data loss
-
The long-term future of Keychain Access and the file-based keychain which it’s centred around
My answer to the first one is clear: If you have to run the legacy app to get at critical data, you should file a bug about that. Even if your bug gets marked as a dup, it’ll allow you to track the status of the original.
Please post your bug number, just for the record.
As to what’s going on at the API level, TN3137 On Mac keychain APIs and implementations talks about this. If you’re using keychain APIs, it’s an important read.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"