home | log | search | bash | stats | wiki

Matches for sha1, 135 total results Sorted by newest | relevance

Tue Mar 01 16:19:47 UTC 2016  <jurov>   deedbot-: http://therealbitcoin.org/ml/btc-dev/attachments/20160301/attachment.txt?sha1=675d9675e9151a4adf860e168aada54d33925369

Sat Feb 27 21:06:09 UTC 2016  <asciilifeform>   4) http://therealbitcoin.org/ml/btc-dev/attachments/20160131/asciilifeform_shiva_fix_flag_bug.vpatch?sha1=8e9f57bf90fc32f4c3bdd88adfb449edd3b93e3c

Sat Feb 27 21:05:52 UTC 2016  <asciilifeform>   3 ) http://therealbitcoin.org/ml/btc-dev/attachments/20160128/asciilifeform_shiva_part_2_of_2.vpatch?sha1=abc9c21e3c86e7a540b20e49a6ebc86017758e48

Sat Feb 27 21:05:34 UTC 2016  <asciilifeform>   2) http://therealbitcoin.org/ml/btc-dev/attachments/20160128/asciilifeform_shiva_part_1_of_2.vpatch?sha1=8d22942ffc97296845fad81c3a78acfdf54af23a

Sun Feb 21 21:56:35 UTC 2016  <ben_vulpes>   Jacmet: another thing worth pointing out are that sha1 and md5 are obsolete

Sun Feb 21 19:56:14 UTC 2016  <ben_vulpes>   my sha1 and md5 match those in k's .sign

Sun Feb 21 19:54:09 UTC 2016  <mod6>   SHA1 & MD5 are broken are they not?

Sun Feb 21 19:46:00 UTC 2016  <mod6>   the md5 & sha1 match the sign file

Sun Feb 21 19:23:45 UTC 2016  <mod6>   heh, these guys built this huge thing, but their sign files only have SHA1 & MD5, even the most recent 2016.02

Sun Feb 21 19:06:07 UTC 2016  <mod6>   anyway, i guess i don't mind, i can add a part where we check the SHA1 & MD5 of the buildroot artifact and then continue to verify that .sign file.

Sun Feb 21 19:03:06 UTC 2016  <phf>   ben_vulpes: they are like md5 and sha1

Wed Feb 17 05:18:51 UTC 2016  <punkman>   like this http://therealbitcoin.org/ml/btc-dev/attachments/20160128/asciilifeform_shiva_part_2_of_2.vpatch?sha1=abc9c21e3c86e7a540b20e49a6ebc86017758e48

Thu Feb 04 16:50:59 UTC 2016  <assbot>   Logged on 04-02-2016 12:02:26; polarbeard: http://log.bitcoin-assets.com/?date=03-02-2016#1395785 << thanks, I've fixed it now, I had no idea it used sha1 by default...

Thu Feb 04 12:02:26 UTC 2016  <polarbeard>   http://log.bitcoin-assets.com/?date=03-02-2016#1395785 << thanks, I've fixed it now, I had no idea it used sha1 by default...

Wed Feb 03 22:40:15 UTC 2016  <assbot>   Logged on 03-02-2016 18:52:30; phf: so there's two sig's that are not sha512. genesis.vpatch.trinque.sig is sha256 and polarbeard_add_getpeerinfo_rpc.vpatch.polarbeard.sig is sha1

Wed Feb 03 18:52:30 UTC 2016  <phf>   so there's two sig's that are not sha512. genesis.vpatch.trinque.sig is sha256 and polarbeard_add_getpeerinfo_rpc.vpatch.polarbeard.sig is sha1

Wed Feb 03 17:40:45 UTC 2016  <jurov>   sha1 because i wanted to track files by contents and sha1 was at hand

Wed Feb 03 17:39:02 UTC 2016  <ascii_butugychag>   jurov: also why do we have sha1 in the mix

Wed Feb 03 17:37:51 UTC 2016  <jurov>   not really, sigs were supposed to carry SHA1 of the patch they apply to

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 ?