mircea_popescu: !!deed http://therealbitcoin.org/ml/btc-dev/attachments/20161031/attachment.txt?sha1=1d162614ad096063e9abb5746b6deab291037beb

mircea_popescu: !!deed http://therealbitcoin.org/ml/btc-dev/attachments/20161101/attachment.txt?sha1=9791c267cc8e30958838c77653f6342a09244fb5

mircea_popescu: in other "holy shit open source" news : to run a linux repo, you must provide... md5hashes for the stuff, because... apt-get wants it. fancy that. and by default you get that and sha1. because it's fucking 1995 and there's a thousand fly eyes!

mircea_popescu: sha1.

mircea_popescu: ya, sure. find me the man who wasn't using sha1 in 2011.

mircea_popescu: mrottenkolber> Naive question: what would be the implications of using sha1 instead of sha512 in vdiff? << roughly speaking you'd be going back in time, we're by and large in the process of moving to sha-3

mircea_popescu: mod6 http://therealbitcoin.org/ml/btc-dev/attachments/20160128/v.pl?sha1=6c20a367bb0788fb6343754f1bd3034a3544c277 << would be this right ?

mircea_popescu: incidentally sha1

mircea_popescu: http://log.bitcoin-assets.com/?date=24-09-2015#1284796 << i suspek that's what they were trying to do with the sha1. ☝︎☟︎

mircea_popescu: <asciilifeform> (what rng? ring oscillator jitter, with sha1 whitening.) <<< better than many

mircea_popescu: asciilifeform yeah, and suppose you see a message from me using sha1 when you know i use sha512.

mircea_popescu: !s sha1

mircea_popescu: btw, cazalla bingoboingo and everyone else in the same situation : if the blob gpg spits out when you sign contains a SHA1 you are using the older, and perhaps not all that secure digest algo. you should move on to sha512 either with --digest-algo SHA512 or else edit gpg.conf to insert personal-digest-preferences SHA512 SHA384 SHA256 ☟︎☟︎

mircea_popescu: decimation here's more. sha1 is implemented as "sha1sum". sha256 however is implemented as "sha256". then sha512 is... "sha512sum"

mircea_popescu: guy reversed sha1, salted sha1 and reversed sha1 within minutes.