Matches for "!s", 11744 total results Sorted by newest | relevance
Thu Jan 21 17:36:22 UTC 2016 <thestringpuller> so if we provide asciilifeform 's meals then he is freed from imprisonment?
Thu Jan 21 15:11:04 UTC 2016 <mod6> <+asciilifeform> if (fHighS && (BN_cmp(sig->s, halforder) < 0)) <+asciilifeform> generally i like to avoid hastening ulcers if possible << yeah, i dont know why I didn't do this to begin with. Heheh.
Thu Jan 21 14:40:07 UTC 2016 <mircea_popescu> in retrospect, i deeply regret not having had the sense of s/ /\t/g back when i made the original genesis commit. but... who knew the future then, and sopmehow being true to source, providing untouched water seemed more important. heck, maybe it was, and the only reason i get to regret doing it is having done it, which keeps me from the more bitter regret of having done it.
Thu Jan 21 13:57:42 UTC 2016 <mircea_popescu> technically mod6's variant, i only removed some spurious tails. but i think you're right.
Thu Jan 21 13:56:57 UTC 2016 <asciilifeform> if (fHighS && (BN_cmp(sig->s, halforder) < 0))
Thu Jan 21 13:56:36 UTC 2016 <asciilifeform> + if (BN_cmp(sig->s, halforder) < 0)
Thu Jan 21 12:42:13 UTC 2016 <jurov> mircea_popescu: afaik DER is just encoding and it's different problem than S value used in signature itself
Thu Jan 21 05:10:35 UTC 2016 <mod6> third high-s tx was malleated also, went through, was confirmed as were previous two
Thu Jan 21 04:49:54 UTC 2016 <mod6> DEBUG DER S: 0xC541A295514D6BF4BEF30599DC7F8A18BEC9B6B3F615D94F847AD154D4DCBB45 << is not
Thu Jan 21 04:47:59 UTC 2016 <mod6> ok second high-s tx went through
Thu Jan 21 04:29:39 UTC 2016 <mod6> yeah, but i guess thats to be expected since these three are supposed to all be high-s.
Thu Jan 21 04:29:12 UTC 2016 <BingoBoingo> Yeah, the active malleation of transactions that happen to be High-S is a pain.
Thu Jan 21 04:28:09 UTC 2016 <mod6> my S value spit out into the debug.log isn't contained in the hex data in the tx: DEBUG DER S: 0xBE8E2E74EBE2618A27D50E0A1D02B33BCE8188940AA22967E9E01AD4D140AB0F
Thu Jan 21 04:22:39 UTC 2016 <mod6> first high-S tx went through o_O
Thu Jan 21 03:54:10 UTC 2016 <mod6> alright, now for the high-S txn
Thu Jan 21 03:45:36 UTC 2016 <mod6> alrighty, 3rd low-S tx made it through
Thu Jan 21 03:40:12 UTC 2016 <mod6> 2nd low-s tx went through
Thu Jan 21 03:09:16 UTC 2016 <mod6> first low-s tx made it through.
Thu Jan 21 01:01:57 UTC 2016 <mod6> thanks for asking. i just went through my high-S enforcement code by hand, and i know for sure that I have an error in there. about to fix it and try that out.
Wed Jan 20 23:51:06 UTC 2016 <shinohai> But - needless distraction for I am sure you need to concentrate the real effort on this S value problem. >.>