Matches for from:mircea_popescu sha1, 10 total results Sorted by newest | relevance
Tue Mar 22 20:33:43 UTC 2016 <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
Tue Feb 02 20:42:25 UTC 2016 <mircea_popescu> mod6 http://therealbitcoin.org/ml/btc-dev/attachments/20160128/v.pl?sha1=6c20a367bb0788fb6343754f1bd3034a3544c277 << would be this right ?
Mon Oct 26 22:09:58 UTC 2015 <mircea_popescu> incidentally sha1
Fri Sep 25 00:28:18 UTC 2015 <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.
Thu Jan 15 01:06:42 UTC 2015 <mircea_popescu> <asciilifeform> (what rng? ring oscillator jitter, with sha1 whitening.) <<< better than many
Sun Nov 09 17:33:03 UTC 2014 <mircea_popescu> asciilifeform yeah, and suppose you see a message from me using sha1 when you know i use sha512.
Sun Oct 26 21:58:55 UTC 2014 <mircea_popescu> !s sha1
Thu Oct 16 14:00:51 UTC 2014 <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
Sun Jul 20 20:49:39 UTC 2014 <mircea_popescu> decimation here's more. sha1 is implemented as "sha1sum". sha256 however is implemented as "sha256". then sha512 is... "sha512sum"
Mon May 12 15:09:21 UTC 2014 <mircea_popescu> guy reversed sha1, salted sha1 and reversed sha1 within minutes.