22:10:54 <m-relay> <s​yntheticbird:monero.social> So
22:10:56 <m-relay> <s​yntheticbird:monero.social> https://hackerone.com/reports/2858802
22:11:10 <m-relay> <s​yntheticbird:monero.social> someone mind explaining
22:11:40 <m-relay> <s​yntheticbird:monero.social> because this fucker of padillac is too lazy to write up about it
22:16:29 <m-relay> <o​frnxmr:xmr.mx> He's not too lazy
22:18:04 <m-relay> <o​frnxmr:xmr.mx> we put out the release and havent heard back from some mining pools yet
22:18:25 <m-relay> <s​pirobel:kernal.eu> maybe read the diff
22:19:20 <m-relay> <s​yntheticbird:monero.social> you mean he partially revealed it the time people update?
22:19:21 <m-relay> <o​frnxmr:xmr.mx> He exposed it on twitter months ago, then went to h1. He wanted to disclose at the time of release, but we waited a week to publicly speak on the issue
22:19:23 <m-relay> <s​yntheticbird:monero.social> i don't think thats how it works
22:20:28 <m-relay> <s​yntheticbird:monero.social> i know, but once you reveal partially you can't go back and reveal it entirely
22:20:32 <m-relay> <s​yntheticbird:monero.social> he said on twitter is just lazy to write up about it
22:22:53 <m-relay> <o​frnxmr:xmr.mx> Finds issue -> tells twitter he found issue -> goes to h1 -> gag order -> release is put out -> pools notified -> gave pools 1 week to update before we publicly announce anything -> 1 week goes by -> release notes updated -> request to disclose (today)
22:23:52 <m-relay> <s​yntheticbird:monero.social> and?
22:25:01 <m-relay> <s​yntheticbird:monero.social> im just saying it would have been nice to reveal it entirely, or at least have someone explain what the vuln was. I don't get why you are giving me the history of how he disclosed it, i was there when he sperged on twitter about it
22:25:07 <m-relay> <o​frnxmr:xmr.mx> And that was a couple hrs ago?
22:25:37 <m-relay> <o​frnxmr:xmr.mx> If its disclosed b4 pools update, we'll lost a majority of our hashrate
22:26:30 <m-relay> <o​frnxmr:xmr.mx> it will be revealed entirely
22:27:31 <m-relay> <s​pirobel:kernal.eu> https://github.com/monero-project/monero/compare/v0.18.3.4...v0.18.4.0
22:27:35 <m-relay> <s​yntheticbird:monero.social> so what, he is just lying about laziness and waiting a few week before writing about it?
22:27:46 <m-relay> <s​pirobel:kernal.eu> https://github.com/bitcoin/bitcoin/issues/27586
22:30:41 <m-relay> <s​yntheticbird:monero.social> (ofrn reacted with a thumbs up irc) ok well i pretty hope he do because vuln fix like that would be interesting to know in details, for you know... other node implementations out there, not giving any name
22:32:57 <m-relay> <o​frnxmr:xmr.mx> we need to (be like zephyr and), attack zephyr, salvium, maybe even zano
22:33:23 <m-relay> <o​frnxmr:xmr.mx> (zephyr knew about the money print bug and didnt tell haven)
22:37:46 <m-relay> <s​yntheticbird:monero.social> you and I aren't on the same wavelength tonight aren't we.
22:38:09 <m-relay> <s​yntheticbird:monero.social> but that's valid lol
23:23:45 <m-relay> <s​pirobel:kernal.eu> probably a cpp issue. rust saved the day again.