[Webkit-unassigned] [Bug 51599] The web process uses its own credential storage

Fri Dec 24 17:16:05 PST 2010

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

--- Comment #17 from Alexey Proskuryakov <ap at webkit.org>  2010-12-24 17:16:05 PST ---
> 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?

> I am going to use bug 51603 to track this.

Thanks for checking! FWIW, it would be easier for me to review a single patch that fixes <rdar://problem/8758386> without introducing regressions than to follow a trail of follow-ups. If it's split into multiple patches, it's harder to keep track of what remains broken.

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