3 ms·

> Absolutely. That is quite the proper response to FreeBSD leaking privileged information about vulnerabilities in the past. And what vulnerability leaks are y

> Absolutely. That is quite the proper response to FreeBSD leaking privileged information about vulnerabilities in the past. And what vulnerability leaks are you talking about?

cperciva 9y ago
I'd like to know this too...
whyever 9y ago
Maybe they are confusing FreeBSD with OpenBSD?
rincebrain 9y ago
They might be mixing up Free and OpenBSD, and thinking of [1], since I can't find any obvious results for FBSD making that mistake. [1] - https://marc.info/?l=openbsd-misc&m=150815942414653&w=2 https://marc.info/?l=openbsd-misc&m=150815942414653&w=2
- cperciva 9y ago
  If that's what it was, they were both mixing up FreeBSD and OpenBSD and had a time machine. OpenBSD has been clear in the past about not respecting embargoes, however. That's their right (Linus takes the same position) but I would completely understand people deciding to not notify OpenBSD as a result. But as far as I'm aware, FreeBSD has an exceptional track record when it comes to respecting vulnerability embargoes.