Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It seems it was made public by accident, so it is not totally surprising that information is sparse :(


Given that I recently received a Debian Security Advisory which specifically addressed this CVE, I don't think it was accidental at all.


I think the timing was accidental due to leaking. The coordinated release became uncoordinated.


The embargo was cancelled half an hour after the leak.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: