The problem I see with that is that it is platform specific. I think that Firefox has it sussed on this one. They use a generic security mechanism that can plug in to different back ends. The default being an internal encrypted store with password. You could then, over time, add additional back ends like the ones you mentioned.
-- Julian Knight www.knightnet.org.uk linux.knightnet.org.uk On Sep 19, 3:11 am, Jo <[EMAIL PROTECTED]> wrote: > I think that the best solution will be to encrypt password like you > were talking using a algorithm for Chromium (available by the svn) and > a different one for Chrome or at least a different encryption key > which will be private/secret to google (not in the svn depot). > > The other concern is about showing password as plain text. One good > solution will be to ask your windows password or your fingerprint (if > you have that kind of stuff installed on your pc) to show you your > passwords. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
