[Webkit-unassigned] [Bug 51599] The web process is using the Mac OS X keychain for HTTP authentication

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=51599





--- Comment #19 from mitz at webkit.org  2010-12-24 17:58:05 PST ---
(In reply to comment #17)
> > I think that there is another loose end here. You changed it so that the web process doesn't read keychain credentials, but it still writes them on its own AFAICT.
> > Setting the preference domain is supposed to prevent this.
> 
> I have a difficulty following this. So, the web process still writes the credentials to Keychain, but in a way that it can't read them, but Safari can? What if the client is not Safari, and it is not signed?
> 
> Or if the web process doesn't write to Keychain any more, then who does?

The UI process should be in charge of read/write access to all permanent credentials, but currently, when a WKCredential with permanent persistence is created in the UI process, it never stores it in the keychain. This, too, will need to be fixed along with this bug.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.