Re: [Fed-Talk] Forcing Safari to use Email Cert
Re: [Fed-Talk] Forcing Safari to use Email Cert
- Subject: Re: [Fed-Talk] Forcing Safari to use Email Cert
- From: Dan Morrison <email@hidden>
- Date: Wed, 14 May 2008 20:40:39 -0600
Richard Murphy wrote:
MY RESPONSE: IS TO LEAVE IT IN KEYCHAINS. IT IS NOT GOOD TO HAVE TO
LOAD CERTIFICATES INTO A BROWSER. KEYCHAINS WAS MADE TO KEEP IT ALL IN
ONE PLACE AND IT CAN BE USED BY ALL
APPLICATIONS I DON'T NEED 5 BROWSERS WITH 5 COPIES OF THE SAME CERTS.
I don't think Tim is suggesting moving the cert store to being
implemented with Safari. Keychains are a subsystem in Mac OS. Keychain
Access is an app to manage Keychain information. As Tim suggests, we
can put some of the management UI into Safari closer to where it's
actually used. That's actually our thoughts for future interfaces as well.
That is exactly right. What Tim, Richard, and I are suggesting is to
allow the Safari UI to provide access to the Keychain objects/settings
that it uses, such that the user does not need to use the Keychain
Access app to modify keychain settings for Safari. There would still be
only one keychain repository. Safari already works this way (it
accesses the Keychain repository), but its UI does not provide access to
(most of) the settings it uses.
Dan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden