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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Amazon.com Security Flaw Accepts Passwords That Are Close, But Not Exact

68 点作者 gaiusparx超过 14 年前

10 条评论

nbpoole超过 14 年前
The comment thread on Reddit, which the article references, is definitely worth reading. There's some good discussion about the difficulties involved in upgrading people's hashes to use a more secure system (eg: <a href="http://www.reddit.com/r/WTF/comments/f96w7/amazon_security_flaw_wtf/c1e9750" rel="nofollow">http://www.reddit.com/r/WTF/comments/f96w7/amazon_security_f...</a>)
tel超过 14 年前
Is there a good way to update passwords to a new encryption scheme? the article tries to ding amazon for failing to do this, but I can't think of a way to reinforce the passwords without announcing that there's a flaw in the implementation. Is there a standard way around this?
评论 #2153997 未加载
评论 #2154096 未加载
评论 #2154016 未加载
johnswamps超过 14 年前
If done deliberately, could this be a useful feature so that users can typo a password (say levenshtein distance &#60;= 1 or 2) and still login? Obviously the major downside is that you would need a longer password to get the same level of security and it could be difficult to implement especially since the password should be hashed. Is this feasible? I'm guessing the answer is no, but was wondering what other people thought.
评论 #2154470 未加载
joshfraser超过 14 年前
My guess is the average Amazon user isn't going over 8 characters and aren't using multi-case passwords to begin with. While stronger passwords would be ideal, most non-savy people are still going with "password", "letmein" and "123456" which aren't secure under any hashing schema.
rabidsnail超过 14 年前
Want to bet they didn't fix this until now because they knew it would lower purchase conversion rate?
pieter超过 14 年前
Passwords on the Dutch banking site ing.nl are also case insensitive, though there hasn't been any public reaction to that.
ronnier超过 14 年前
I reported the same flaw for <a href="http://utd.edu" rel="nofollow">http://utd.edu</a>. They didn't seem to care.
goombastic超过 14 年前
This sounds like a feature to me. :)
CamperBob超过 14 年前
What exactly does this hurt? It cuts down on customer-support traffic, makes life easier for the user, and (as far as I can imagine at least) doesn't make anyone any more vulnerable. Under a fuzzy comparison scheme, weak passwords are still weak, and strong passwords will still be strong.
评论 #2154180 未加载
评论 #2154187 未加载
earl超过 14 年前
I couldn't replicate the article's results for the 8 character cutoff, but I did verify my password is case insensitive. For the record, I registered in 1996 or so, and probably haven't changed my password since.
评论 #2154605 未加载
评论 #2154029 未加载