TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

We can do better – Please fix plaintext credential storage in Chrome

13 点作者 shayanjm将近 10 年前

3 条评论

mukyu将近 10 年前
This article is simply incorrect. The passwords are only stored in plaintext when there are no OS-level or desktop environment options available to protect them.[0] In the absence of such a system where exactly do you expect Chrome to store the encryption key for the list of passwords?<p>[1] <a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;chromium&#x2F;wiki&#x2F;LinuxPasswordStorage" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;chromium&#x2F;wiki&#x2F;LinuxPasswordStorage</a><p>edit: Apparently there are people that run either incredibly old versions of chrome or don&#x27;t run a keystore daemon and actually upload all of their dotfiles to github so I guess that part is technically accurate.
评论 #9800743 未加载
sbierwagen将近 10 年前
Okay, so it&#x27;s possible someone might accidentally publish their passwords with an unwise git commit, but has anyone <i>actually done this?</i> Can anyone point to a real life example?
评论 #9798768 未加载
ufoolme将近 10 年前
Once the attacker has the username, password and access to the computer, the game is already over. I can&#x27;t see how adding anything on top is nothing but smoke and mirrors.
评论 #9798849 未加载