nitter
PaX Team
@paxteam
pax.grsecurity.net/
Joined February 2010
Tweets
548
Following
2
Followers
2,766
Likes
35
Tweets
Tweets & Replies
Media
Search
Load newest
PaX Team
@paxteam
19 Nov 2017
Torvalds' rants about the incompetence of the KSPP:
lkml.org/lkml/2017/11/17/423
and
lkml.org/lkml/2017/11/17/767
. no wonder linux security suffers from both sides as the end result. the 90's idea of debugging == security has been dead ever since.
1
20
3
43
PaX Team
@paxteam
15 Oct 2017
two tidbits about CVE-2017-5123: it's also a KASLR break (quiz: how?) and UDEREF on i386 makes it harmless (SMAP/etc are vulnerable).
2
6
7
PaX Team
@paxteam
26 Sep 2017
perhaps @kurtseifried wants to chime in with another completely unwarranted CVE? :)
grsecurity
@grsecurity
26 Sep 2017
#grsecurity
/PaX never affected by
seclists.org/oss-sec/2017/q3…
even prior to 2015 fix (which RHEL 6/<7.4 didn't apply), has separate ET_DYN base
1
1
5
PaX Team
@paxteam
19 Jun 2017
Red Hat's @kurtseifried thinks that 200 hours of brute force is a defense failure. smells like sour grapes for having ignored the problem.
2
4
PaX Team
@paxteam
19 Jun 2017
An Ancient Kernel Hole is (Not) Closed:
grsecurity.net/an_ancient_ke…
. A lesson in real non-embargoed security.
66
3
57
PaX Team
@paxteam
5 Jun 2017
the KSPP's way of building their 'community' is to start banning the most potent contributors over the broken ego of Daniel Micay.
Bruce Leidl
@bleidl
5 Jun 2017
Hi strcat, it's easy to ban me from #
#linux
-hardened IRC for no reason but are you also able to ban me from ring 0 👇
6
13
PaX Team
@paxteam
3 Jun 2017
we do not tolerate blatant copyright violations from the Kernel Self Protection Project anymore:
openwall.com/lists/kernel-ha…
10
97
10
125
PaX Team
@paxteam
11 May 2017
restoring balance to the force:
openwall.com/lists/kernel-ha…
2
44
6
57
PaX Team
@paxteam
26 Apr 2017
We are passing the baton:
grsecurity.net/passing_the_b…
10
102
13
61
PaX Team
@paxteam
23 Apr 2017
a new blog from spender about CVE-2017-NOTREALLY
grsecurity.net/the_infoleak_…
52
1
60
PaX Team
@paxteam
10 Mar 2017
it was proactively 'fixed' by
tedunangst.com/flak/post/my-…
in 2013. a lesson in unforeseen consequences.
PaX Team
@paxteam
10 Mar 2017
dear 'other side', brace yourselves for the consequences of
gcc.gnu.org/git/?p=gcc.git;a…
:)
2
6
PaX Team
@paxteam
10 Mar 2017
it was introduced by
gcc.gnu.org/git/?p=gcc.git;a…
in 2001.
PaX Team
@paxteam
10 Mar 2017
dear 'other side', brace yourselves for the consequences of
gcc.gnu.org/git/?p=gcc.git;a…
:)
4
2
PaX Team
@paxteam
10 Mar 2017
dear 'other side', brace yourselves for the consequences of
gcc.gnu.org/git/?p=gcc.git;a…
:)
7
2
14
PaX Team
@paxteam
18 Feb 2017
dear infosec thought leaders: get your revenge by emailing spender@ with your testimonial about our technology for the revamped grsec site.
1
10
8
PaX Team
@paxteam
6 Feb 2017
today's grsecurity release for linux 4.9 adds the promised return checking to the public version of RAP:
grsecurity.net/rap_announce_…
@epakskape
3
97
2
74
PaX Team
@paxteam
14 Dec 2016
undergrad C test by the linux stable series maintainer (
@gregkh
):
openwall.com/lists/kernel-ha…
1
8
6
PaX Team
@paxteam
1 Oct 2016
there're many bugs our defenses caught over the years, just browse lkml or our forums.
1
PaX Team
@paxteam
1 Oct 2016
sure, it's proven itself time and again, not many defenses can say the same.
1
PaX Team
@paxteam
1 Oct 2016
@lolhaq
@Snowden
@subgraph
@QubesOS
@marcan42
that's a great example of how our defenses protect against even our own bugs. thanks!
2
PaX Team
@paxteam
12 Jun 2016
since you asked us about Intel's CET:
forums.grsecurity.net/viewto…
3
109
97
Load more