I was technically incorrect in the fact that they tried to work around a bug in their compiler plugin and instead broke the code?
-
-
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 @lazytyped and
And I have no idea what you're talking about re: ASLR. Citation needed.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
In case you haven't seen it and are just parrotting
@paxteam, this is the "source" for my "incorrect" solution: https://forums.grsecurity.net/viewtopic.php?f=3&t=4342 …1 reply 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
In other words, I made a small comment on the need for a signed type in the original code. That's it.
@paxteam fixed it a different way.1 reply 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
I don't care enough to argue the pros and cons of various solutions, so I didn't bother analyzing it or starting an argument. It was fixed.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
But enough to assume that they don't test nor do quality development (when instead the track record proves the opposite)? Funny.
2 replies 0 retweets 0 likes
Again, it's obvious they *didn't* test that change. I have no idea how you can even begin argue the opposite.
-
-
Replying to @marcan42 @lazytyped and
And they obviously didn't *try* to repro it either, because I was able to come up with a tweet-sized repro in 5 minutes.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.