By default, Chromium uses its own unencrypted password store. However, as seen on other distros (confirmed on ubuntu), chromium can use gnome-keyring or kwallet instead to store passwords (both of which bring the opportunity to lock the password store and encrypt). While users can put something in ~/.bash_profile, to me it makes more sense if the ebuild added the file: /etc/chromium/default with the following line in it: CHROMIUM_FLAGS="--password-store=detect" There is one complication to switching: old passwords in the default password store will not be automatically migrated. For more details please see: http://www.tankmiche.com/tips/chromium-keyring/
According to bug 348402, --password-store=detect is enabled by default in the chromium-10 series. Still, your suggestion is an interesting alternative; I will let phajdan.jr take a look rather than resolving this as a dup.
(In reply to comment #1) > According to bug 348402, --password-store=detect is enabled by default in the > chromium-10 series. > > Still, your suggestion is an interesting alternative; I will let phajdan.jr > take a look rather than resolving this as a dup. Good. Seemant, please consider unmasking chromium-10 which has the new defaults. I'm reluctant to modify the behavior for earlier versions of the browser. I believe that different distributions patching and changing things actually cause more confusion. There were some reports about "detect" option not working reliably before version 10. *** This bug has been marked as a duplicate of bug 348402 ***
