]> git.ipfire.org Git - thirdparty/tor.git/commit
Revise proposal 162: SHA256(x), not SHA256(SHA256(x))
authorNick Mathewson <nickm@torproject.org>
Wed, 23 Sep 2009 15:45:54 +0000 (11:45 -0400)
committerNick Mathewson <nickm@torproject.org>
Thu, 15 Oct 2009 19:17:13 +0000 (15:17 -0400)
commit0bce0161dded650ac6fa665a7b861d6faac9e91c
tree2c4b465774c40101044b1eb4d2f4e360e3a4f4b7
parent3471057486a8aef0be6e74b090a3173e0794c84b
Revise proposal 162: SHA256(x), not SHA256(SHA256(x))

The point of doing SHA256 twice is, generally, is to prevent message
extension attacks where an attacker who knows H(A) can calculate
H(A|B).  But for attaching a signature to a document, the attacker
already _knows_ A, so trying to keep them from calculating H(A|B) is
pointless.
doc/spec/proposals/162-consensus-flavors.txt