226 entries in 0.814s
assbot: -----BEGIN PGP SIGNED MESSAGE----- Hash:
SHA1 Testing - -----BEGIN - Pastebin.com
assbot: -----BEGIN PGP SIGNED MESSAGE----- Hash:
SHA1 NO CONSPIRACY AT ALL 1 36 3 - Pastebin.com
assbot: -----BEGIN PGP SIGNED MESSAGE----- Hash:
SHA1 NO CONSPIRACY AT ALL 1 36 3 - Pastebin.com
assbot: -----BEGIN PGP SIGNED MESSAGE----- Hash:
SHA1 NO CONSPIRACY AT ALL 1 36 3 - Pastebin.com
MolokoDesk: I think the
sha1 test case I was using wasn't in WoT at the time is why I've never noticed one before.
assbot: -----BEGIN PGP SIGNED MESSAGE----- Hash:
SHA1 What words say does not last. - Pastebin.com
mircea_popescu: decimation here's more.
sha1 is implemented as "sha1sum". sha256 however is implemented as "sha256". then sha512 is... "sha512sum"
assbot: -----BEGIN PGP SIGNED MESSAGE----- Hash:
SHA1 - -----BEGIN PGP SIGNED MESSAG - Pastebin.com
mircea_popescu: guy reversed
sha1, salted
sha1 and reversed
sha1 within minutes.
bitcoinpete: and i don't completely see why publishing a hash of just the answer shouldn't work. is it that easy to reverse
sha1?
tg2: brb
sha1 1024 gpg key inbound
Neil_: Hehe, SEC uses
SHA1 hashes.
Scrat: /dev/urandom uses
sha1, if someone can preimage
sha1 at will you're in deep doodoo
jurov: ;;google md5
sha1 speed
jurov: got better idea - use
sha1(btc_addy+mpsic) : balance
jurov: the
SHA1 formula is too big
jurov: maybe there's a bounty to make
sha1 collision of meaningful strings.. so you'll get rewarded then
jurov: lol, worrying about
sha1(order+signature) collisions... it's like mpex is going to become used across whole multiverse
jurov: there will be much sooner bit flip from cosmic rays than
sha1 collision
smickles: kakobreklaaa: you're still on
sha1?