@grsecurity I'm just trolling a bit because the bug is really sad; you're the one randomly blocking people like a crying kid. Man up.
Seems the commercial oh-so-exclusive "stable" @grsecurity kernel was also affected by the aforementioned DoS (it also got updated).
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@grsecurity I didn't analyze the whole thing; had I done so I'd have provided a complete fix patch instead of a mere "maybe ssize_t" comment -
@grsecurity I like some of the stuff you do, but you need to learn to take pointed criticism as easily as you dole it out. Nobody's perfect.
End of conversation
New conversation -
-
-
@grsecurity "I crashed grsec by accident and here's how you can too" isn't FUD, it's an objective fact. -
@grsecurity I'm not normally an ass about bug reports, but this particular one reeks of carelessness, and this is a _security_ patchset.
End of conversation
New conversation -
-
-
@grsecurity The existing code was *fine* but triggered a *false positive* using S_O. The patched code was *broken* *and* triggered S_O. -
@grsecurity So not only did you not fix the bug (i.e. patch was not tested), but made things worse by introducing brokenness if !S_O.
End of conversation
New conversation -
-
-
@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. - Show replies
New conversation -
-
-
@marcan42 I thought that grsecurity blocked you. How is s/he replying? -
@drscriptt You can still view tweets from a blocked user if you want. - Show replies
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.