You do realize that in that conversation (which undoubtedly went bad), you were technically incorrect? :)
-
-
Replying to @lazytyped @_pablosole_ and
I was technically incorrect in the fact that they tried to work around a bug in their compiler plugin and instead broke the code?
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
You were incorrect on the solution (the big was ack'ed and fixed), just like you were incorrect on that ASLR "vulnerability" before
1 reply 0 retweets 0 likes -
Replying to @lazytyped @_pablosole_ and
I made a minor suggestion regarding the type; I never emphasized it as "the" solution (and I never intended it to be authoritative)
1 reply 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
@paxteam just decided to latch onto that in order to attempt to discredit me, because he has no defense for the actual original problem.1 reply 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
The actual issue here is that grsecurity/paxteam obviously neither review nor test their patches. They never even bothered to repro the bug.
3 replies 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
That's ridiculous. Bugs happen. The track record in terms of issues proves the exact opposite. Seems like you've never done any dev of sort
1 reply 0 retweets 2 likes -
Replying to @lazytyped @marcan42 and
With this attitude and jumping to conclusion, I'm surprised you feel like you can call out others on badly interacting :)
1 reply 0 retweets 0 likes -
Replying to @lazytyped @_pablosole_ and
It's *obvious* that they didn't test the code because it *didn't* fix the original problem and made it *worse*.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
Or are you suggesting that they tested it, saw that it was broken, and shipped it anyway?
1 reply 0 retweets 0 likes
Replying to @marcan42 @lazytyped and
I mean, I don't know about you, but when I get a bug report I *repro* it before randomly pushing an untested fix that makes things worse.
7:50 AM - 28 Apr 2017
0 replies
0 retweets
0 likes
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.