I couldn't agree more, but it has a long way to go, and there are lots of bugs in Keychain.A step in the right direction. There is nothing I would like to see Apple do more than to overhaul Keychain into a full-featured password manager app and give 1Password a run for their money.
Sorry, but you're wrong about "no bugs". There are lots of them.It works, there's no bugs, but it's just not consumer-friendly. Most Mac users that I know don't even know about it.
I agree about the passwords in Safari prefs. I can't understand that either. There should be only ONE password store.A most relevant point of thought to me is the unification of passwords and autofill info. I cannot understand why seemingly, passwords are to be separately saved inside the preferences of Safari while these are also in the keychain (app and file I mean). It appears that this info is synced within Safari trough iCloud, separately and independently of the keychain sync in iCloud, be that feature activated or not.
The System Keychain and Login keychain are used for separate purposes. The Login keychain are for your personal passwords, while the System keychain are for system stuff. For example the Time Machine password is stored in the System keychain, because Time Machine is used to backup ALL users accounts, not just a specific user. The backup should work, no matter who is logged in to the computer.To take a walk in the backyard of the topic, I also find it similarly irrelevant to have a system keychain and an login keychain within the keychain app. Double items are to be found there yet again.
If there are passwords stored in both System and Login, then I'd consider that as a bug.
I agree.And to finish off this train of thought: what are passwords on iOS doing in the Settings app, and why not place it parallel inside Mac OS, or the other way around...?
There are many more bugs in Keychain.Keychain has a huge bug, if you don't use Icloud it stores your safari passwords in a Local Items section, whenever you upgrade to a new OS or migrate to a new computer it erases all of those passwors and resets with a new Local Items folder.
https://forums.macrumors.com/threads/data-migration-local-keychain-passwords-not-appearing.1905840/
Let's say that I log into https://example.com
Then the password is stored twice. Once for https and once for http, for the same domain.
It has happened that only one of them got updated, so that the other one has an old password.
I think the password should only be stored ONCE per domain. If I change my password for example.com, how big is the chance that I would want separate passwords for the http and https? That should never happen.
Another bug is that I sometimes run macOS in my native language Swedish and sometimes in English, and then the password is stored also per language. So if I have logged in to example.com in English, then I get one entry for https://example.com and one for http://example.com, but the I also get a new password stored for both of these, when I run macOS in Swedish, so now I have two entries for https and two for http, for the single domain example.com. If I change my password while running in Swedish, then only two passwords for the domain gets updated, so when I switch back to English, I have the two old passwords.
Then there's the bug with multiple "iMessage Singing Key". I often get lots of them. Does iMessage really generate a new key for every message sent? I think the same key should be used to sign all of my messages, until I choose to erase the key and generate a new key, in which case it should replace the old key.