3 ms·

Thanks for the great work and swift communication I'm very disappointed to hear that the researchers did not disclose these findings to the OpenBao project bef

Thanks for the great work and swift communication I'm very disappointed to hear that the researchers did not disclose these findings to the OpenBao project before publishing them, so you now have to rush a release like this Will you reach out to the researchers for an explanation after you've fixed the issues?

wafflemaker 1y ago
I can explain* researchers (and myself, though have nothing to do with it): We both learned about OpenBao today. explanation ≠ excuse
- Scandiravian 1y ago
  Thank you for the explanation. It's obviously not great that this was missed, but finger-pointing now doesn't really help anyone, so I'll focus on what seems to me like the root issue My impression is that there is an information gap about forked projects that lead to this issue I'm on vacation right now, but when I'm back I'll try to setup a small site that lists forks of popular projects and maybe some information on when in time the project was forked Hopefully something like that can make it more likely that these things are responsibly disclosed to all relevant projects