Seems the commercial oh-so-exclusive "stable" @grsecurity kernel was also affected by the aforementioned DoS (it also got updated).
@grsecurity I never asserted any of those 3 as fact. I wondered why code review failed, whether it might be exploitable, etc.
-
-
@grsecurity The broken code is *not* obviously safe. It's injecting characters >buffer capacity. I think the underlying indexing saves you. -
@grsecurity But making the same mistake elsewhere could easily lead to a buffer overflow vuln. That's Bad™.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.