This looks like a Feature Request.

Could some from Dev team please look into this feature request.

Thank you.

Just for context, this is a tricky area: even with requiring authentication for password viewing in chrome://settings/passwords, passwords are still easy to snoop for a local attacker via DevTools, bookmarklets, misusing sync or inspecting the local storage. Chrome is not defending against the local attacker [1]. Reauthentication on the settings page might improve privacy, but the security impact is questionable (people might misunderstand that "protection"). Note that passwords.google.com does not have this problem: the website itself never causes the passwords to be stored on the local device, so there the reauthentication is indeed a good security measure.

Having said that, in the past, the decision has been to provide reauthentication in the settings for privacy purposes. It is there for Win and Mac, and will be there for mobile once we launch viewing passwords there. So we should add it for Linux and CrOS as well.


[1] https://www.chromium.org/Home/chromium-security/security-faq#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-

There should be some way. Some of which I could figure out is encrypting
the localstorage database which is stored in sqlite3 format.
The database is locked when chrome is using it, but not when chrome is
closed. So, encrypting it can be a way.

The implementation can be similar to the way passwords for user accounts
are stored on your computer.

Another way I would suggest is to provide some cross-platform *keyring*
tool that could save passwords. For example, *Seahorse* and *KWallet* can
be used on Linux to store passwords and those wallets are not accessible
without your password. So, there's a safety feature for Linux.

There is similar *keychain* tool for Apple systems.

Windows has it's own credential system (which anyone hardly uses).
And this ignites with an idea of a keyring system for all devices including
Android. How's that?

Those are different tools for different platforms and intergrate with other
software in different ways. If such feature is built into chrome which
makes it available cross-platform or available tools like Seahorse are
forked to be available cross-platform it would be a great feature.
That's a suggestion.

"*Chromium is open source. So being a student I would had definitely
contributed if I had a considerable level of expertise."*

Ad #3 -- this is way beyond the scope of this feature request. Chrome is not meant to replace the OS (except on Chrome OS), it is a web browser.

Once you are ready to make the code contribution, you are of course free to start a new bug and discussion with our security team, if you have a concrete plan for improving security.

Thanks vabr!
Got it.
You can now close the issue. :)

Thanks!