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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Jacob Appelbaum: attackers got certs for *.*.com and *.*.org

8 点作者 rw超过 13 年前

2 条评论

ynoclo超过 13 年前
RFC2818 (the 'HTTP over TLS' specification) says that names may contain the wildcard character, which is considered to match any single domain name component or component fragment. E.g., *.a.com matches foo.a.com but not bar.foo.a.com. f*.com matches foo.com but not bar.com.<p>A careful reading of this wording does not seem to rule out the use of more than one wildcard, e.g. '*.*.com'. That's unfortunate. It likely depends on the particular browser's TLS implementation as to whether more than one wildcard in a name would be processed.
0x0超过 13 年前
So would those certs be accepted by normal browsers? Couldn't the public suffix list be used to reject such overlay broad wildcards?