<s​yntheticbird:monero.social> So

<s​yntheticbird:monero.social> hackerone.com/reports/2858802

<s​yntheticbird:monero.social> someone mind explaining

<s​yntheticbird:monero.social> because this fucker of padillac is too lazy to write up about it

<o​frnxmr:xmr.mx> He's not too lazy

<o​frnxmr:xmr.mx> we put out the release and havent heard back from some mining pools yet

<s​pirobel:kernal.eu> maybe read the diff

<s​yntheticbird:monero.social> you mean he partially revealed it the time people update?

<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

<s​yntheticbird:monero.social> i don't think thats how it works

<s​yntheticbird:monero.social> i know, but once you reveal partially you can't go back and reveal it entirely

<s​yntheticbird:monero.social> he said on twitter is just lazy to write up about it

<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)

<s​yntheticbird:monero.social> and?

<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

<o​frnxmr:xmr.mx> And that was a couple hrs ago?

<o​frnxmr:xmr.mx> If its disclosed b4 pools update, we'll lost a majority of our hashrate

<o​frnxmr:xmr.mx> it will be revealed entirely

<s​pirobel:kernal.eu> github.com/monero-project/monero/compare/v0.18.3.4...v0.18.4.0

<s​yntheticbird:monero.social> so what, he is just lying about laziness and waiting a few week before writing about it?

<s​pirobel:kernal.eu> bitcoin/bitcoin #27586

<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

<o​frnxmr:xmr.mx> we need to (be like zephyr and), attack zephyr, salvium, maybe even zano

<o​frnxmr:xmr.mx> (zephyr knew about the money print bug and didnt tell haven)

<s​yntheticbird:monero.social> you and I aren't on the same wavelength tonight aren't we.

<s​yntheticbird:monero.social> but that's valid lol

<s​pirobel:kernal.eu> probably a cpp issue. rust saved the day again.