> Why? Because that's a false sense of security. Chrome would have to also store the encryption key, and store it in the same place and under the same access controls as the encrypted data.
I hear you, but this is not the case with Safari. It offers secure local storage. It's the securesettings API. It uses the OS level encryption, and, based on the current state of play, this does not appear to be compromised.
> as shown by the fact that malware (and legitimate programs!) can read the Firefox local password database.
Is this also the case for Safari? I have not read anything to this effect.