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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

OpenSSL DSA key recovery attack

184 点作者 bqe将近 9 年前

2 条评论

zaroth将近 9 年前
<i>Make Sure DSA Signing Exponentiations Really are Constant-Time</i><p>&quot;...the OpenSSL team committed two code changes relevant to this work. The first adds a “constant-time” implementation of modular exponentiation...&quot;<p>&quot;The execution time of the “constant-time” implementation still depends on the bit length of the exponent, which in the case of DSA should be kept secret [12, 15, 27]. The second commit aims to “make sure DSA signing exponentiations really are constant-time” by ensuring that the bit length of the exponent is fixed.&quot;<p>&quot;...While the procedure in this commit ensures that the bit length of the sum kq is fixed, unfortunately it introduces a software defect. The function BN_copy is not designed to propagate flags from the source to the destination. In fact, OpenSSL exposes a distinct API BN_with_flags for that functionality...&quot;<p>&quot;In contrast, with BN_copy the BN_FLG_CONSTTIME flag does not propagate to kq. Consequently, the sum is not treated as secret, reverting the change made in the first commit...&quot;<p>Exploitation requires a local &#x27;spy&#x27; process recording timing signals while the handshakes are running. I assume this is an unprivileged process, otherwise wouldn&#x27;t the key be directly accessible?
评论 #11884326 未加载
评论 #11884102 未加载
评论 #11884114 未加载
vessenes将近 9 年前
Needs to listen to only a few hundred handshakes. Ugh. Something tells me this could be deployed on AWS large instances with some success.
评论 #11888527 未加载