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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

What changed in OpenSSL after heartbleed

158 点作者 gnu将近 5 年前

7 条评论

zdw将近 5 年前
I&#x27;d be more interested in a comparison in the strategies used to harden the codebase in the forks like BoringSSL and LibreSSL, and how well those strategies have panned out.<p>There has historically been some crowing from the LibreSSL crowd about how their work avoided CVE&#x27;s later discovered in OpenSSL: <a href="https:&#x2F;&#x2F;undeadly.org&#x2F;cgi?action=article&amp;sid=20150319145126" rel="nofollow">https:&#x2F;&#x2F;undeadly.org&#x2F;cgi?action=article&amp;sid=20150319145126</a>
评论 #23873642 未加载
juanbyrge将近 5 年前
Code quality and hygiene mean absolutely nothing if you have a large number of academic types who use OpenSSL as the dumping ground for their pet research projects, that are enabled by default, of course.<p>Also, OpenSSL supports all kinds of ancient esoteric platforms that are essentially unused, yet were kept in the code base for sentimental reasons.<p>The real metric they should be looking at is the number of features&#x2F;platforms&#x2F;LOC removed from the project. Less code = less surface areas for exploits.
评论 #23876040 未加载
评论 #23875145 未加载
评论 #23875307 未加载
评论 #23878408 未加载
评论 #23874349 未加载
easterncalculus将近 5 年前
I&#x27;m glad there have been changes to the project. Heartbleed was certainly bad, but I personally never understood getting behind LibreSSL. Seeing one bad vulnerability from an established project and immediately jumping ship to a brand new one with less eyes and reputation seemed hasty to me.
评论 #23872692 未加载
评论 #23874555 未加载
评论 #23872633 未加载
评论 #23872451 未加载
评论 #23872992 未加载
icefo将近 5 年前
This made me think of BoringSSL and LibreSSL again.<p>Looking up on Wikipedia it seems that LibreSSL is focused on OpenBSD and removed lots of legacy code. BoringSSL (Google) got renamed to Tink but I couldn&#x27;t not find much more.<p>It&#x27;s sad to see that duplication of effort but it&#x27;s also the force of open source
评论 #23872516 未加载
评论 #23872551 未加载
评论 #23873498 未加载
评论 #23872481 未加载
评论 #23873681 未加载
评论 #23879487 未加载
评论 #23873318 未加载
caiobegotti将近 5 年前
For random reasons I can&#x27;t read the full article but I wonder if they discuss the impact of LibreSSL on OpenSSL itself. Would anyone who moved to LibreSSL actually look back to OpenSSL today in 2020? Honest question as I&#x27;m not a crypto professional myself.
评论 #23872434 未加载
rshnotsecure将近 5 年前
OpenSSL recently passed a change in their vuln announcement policy to give a major firm, which everyone here knows I think, 7 days advance notice of any zero-day that they were made aware of.<p>This was the engineer who helped set up the new policy: <a href="https:&#x2F;&#x2F;awe.com" rel="nofollow">https:&#x2F;&#x2F;awe.com</a><p>To be honest, maybe it&#x27;s a good idea. It depends on how much support Huawei is willing to give OpenSSL.
评论 #23873662 未加载
评论 #23875156 未加载
dyingkneepad将近 5 年前
What&#x27;s the current market share of OpenSSL vs LibreSSL vs alternatives?