Camino used to work that way, but I think this new way, where the passwords are interoperable between Camino and Safari (with the downside that Safari can remove them) works better... there really should be no functional difference between a saved password for Camino and Safari, and you shouldn't have to save it twice.
Mike. -- Mike Nguyen [EMAIL PROTECTED] nguyenhm16 (AIM) 281-788-6453 (cell) Legum servi sumus ut liberi esse possimus. -Cicero On Monday, March 10, 2008, at 09:31AM, "Noemi" <[EMAIL PROTECTED]> wrote: > >OK... > >It's clearly possible to create keychain entries that Safari can't >read, as evidenced by all the other apps that don't lose their >passwords when Safari is reset. Why does Camino create entries that >Safari can read? > >Thanks for answering my questions about this. > > >On Mar 10, 2008, at 10:12 AM, Stuart Morgan wrote: > >> On Mar 9, 2008, at 8:08 AM, Noemi wrote: >> >>> Wait, resetting *Safari* causes one to lose Camino passwords? *Mind >>> boggles.* Is that going to be a permanent "feature"? >> >> We use the standard OS password storage system as it is intended to be >> used, which is a feature, and is permanent. As for whether Safari will >> always choose to remove anything in that store that it can read >> (rather than just things it created, as Camino does) is something >> you'd have to ask Apple, since we don't control Safari development. >> >> -Stuart >> _______________________________________________ >> Camino mailing list >> Camino@mozdev.org >> https://www.mozdev.org/mailman/listinfo/camino > >_______________________________________________ >Camino mailing list >Camino@mozdev.org >https://www.mozdev.org/mailman/listinfo/camino > > _______________________________________________ Camino mailing list Camino@mozdev.org https://www.mozdev.org/mailman/listinfo/camino
