Bitcointalk · Hash() function not secure

中本聪,2010 年 7 月 16 日

SN-1196 已核对来源,附原文与上下文。

阅读语言
中文译文

SHA256 不同于从 128 位到 160 位那一步。

打个比方,它更像从 32 位到 64 位地址空间那一步。16 位计算机的地址空间我们很快用完了,32 位计算机在 4GB 处用完了,但这不意味着 64 位也会很快用完。

在我们有生之年,SHA256 不会被摩尔定律式的算力提升攻破。倘若它会被攻破,那会是某种突破性的破解方法。能把 SHA256 打压到计算上可行范围的攻击,很可能也会顺带重创 SHA512。

倘若我们看到 SHA256 的弱点在逐渐显现,可以在某个区块号之后过渡到新的哈希函数。所有人必须在那个区块号之前升级软件。新软件会给所有旧区块再存一个新哈希,确保它们不会被换成另一个带相同旧哈希的区块。

ORIGINAL · 英文原文
SHA256 is not like the step from 128 bit to 160 bit.

To use an analogy, it's more like the step from 32-bit to 64-bit address space.  We quickly ran out of address space with 16-bit computers, we ran out of address space with 32-bit computers at 4GB, that doesn't mean we're going to run out again with 64-bit anytime soon.

SHA256 is not going to be broken by Moore's law computational improvements in our lifetimes.  If it's going to get broken, it'll be by some breakthrough cracking method.  An attack that could so thoroughly vanquish SHA256 to bring it within computationally tractable range has a good chance of clobbering SHA512 too.

If we see a weakness in SHA256 coming gradually, we can transition to a new hash function after a certain block number.  Everyone would have to upgrade their software by that block number.  The new software would keep a new hash of all the old blocks to make sure they're not replaced with another block with the same old hash.
上下文
← 上一条 SN-1196 · 当前 下一条 → 在档案中查看完整主题串 →
来源
Bitcointalk 原始链接 ↗ 记录编号 SN-1196