Insults? You clearly haven't produced code at some degree, or you'd have a more mature approach
-
-
Replying to @lazytyped @marcan42 and
I'm sorry if calling out your bullshit makes you rage quit. But it's fine by me.
1 reply 0 retweets 1 like -
Don't worry, my code is present on more devices than grsecurity. I don't need personal validation from a random person on Twitter ;)
1 reply 0 retweets 0 likes -
Great, then don't get too heated. I mean no disrespect when I state that your comments about testing show lack of experience
1 reply 0 retweets 1 like -
Replying to @lazytyped @marcan42 and
(or you have experience, but you are trying to pursue an agenda, which is IMHO a bit worse, but understandable)
2 replies 0 retweets 0 likes -
Replying to @lazytyped @bleidl and
arguments that ppl just came to exactly same solution ∗after∗ having read someone else's are disturbing
2 replies 0 retweets 2 likes -
Replying to @bsdaemon @lazytyped and
We're talking about things like noticing a particular random value isn't properly random due to a bug and fixing it.
1 reply 0 retweets 0 likes -
*Nobody* has read *all* of grsecurity. The person who found that bug had *no clue* it was fixed in grsec too. (the non-grsec fix was better)
4 replies 0 retweets 1 like -
Keep in mind these are *patches*. They aren't new code. Much of grsec is wide-ranging cleanup/micro-patching of existing kernel code.
1 reply 0 retweets 0 likes -
Okay, I'm out. We need a better venue than twitter as there's too much to explain here.
1 reply 0 retweets 0 likes
Replying to @lazytyped @bsdaemon and
I agree that Twitter is probably the worst possible medium to have this conversation.
6:49 AM - 5 Jun 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.