Viewing profile — PaXTeam
PaXTeam
HN member- Joined
- Wed, Apr 26, 2017, 2:35 PM UTC
- HN karma
- 20
- Public activity
- 15 items
- HN profile
- View on Hacker News ↗
About PaXTeam
No profile information was provided.
Recent public activity
-
comment
Comment #17255031
1. both insertReturnProtectorPrologue and insertReturnProtectorEpilogue check hasReturnProtectorTempRegister before proceeding with the instrumentation. so either the changes to ca…
-
comment
Comment #17252154
this is basically the xor canary approach originally pioneered by the Stackguard guys (i'm pretty sure you were already around at the time though probably forgot such old history a…
-
comment
Comment #14226703
> Sorry, I assumed that 80% and 86% were close enough that a reasonable reader would be able > to see that I had mis-remembered the second significant figure for statistics I heard…
-
comment
Comment #14219015
> Sorry, it's 86% and 14% in Linux 4.11. It's literally in the link I posted. you first quoted 80% and chided me for not reading the article linked to because it supposedly implied…
-
comment
Comment #14218474
can you quote Greg back on your "At most 80% of Linux contributors have jobs at software companies" because i don't see it in there? and you can add the source for your 20% while a…
-
comment
Comment #14215568
> 1000 small commits can add up to 100 small+simple components vs. > Commits might be patches, but they're sure not components. make up your mind, are components (whatever that mea…
-
comment
Comment #14215518
and the source of those numbers is...? > As for grsecurity, 100% of the core grsecurity team (that work at "Open Source Security") are paid for their work. that's 100% false. both …
-
comment
Comment #14208458
careful there, the author line doesn't imply authorship (if it does, the upstream kernel is already violating our copyrights).
-
comment
Comment #14208447
i don't quite get what you're arguing now... are you stating that when there're functional dependencies between components, we should somehow ignore them when incorporating them in…
-
comment
Comment #14208423
i don't think you read carefully what i replied to so here's it again: > The problem is that getting things into small individually testable components > is literally anathema to t…
-
comment
Comment #14208346
> What do you mean, the Linux kernel isn't developed for free? Many contributors aren't paid. you're wrong, see item 6 in https://opensource.com/article/16/12/yearbook-9-lessons-25…
-
comment
Comment #14205444
> The problem is that getting things into small individually testable components > is literally anathema to the Pax/grsecurity model. no, you're wrong. how do you think we develope…
-
comment
Comment #14205323
what, do you have 'real evidence' that we're the same person? if so i'd like to see it and also know how we pulled off our appearance at H2HC a few years ago. let me guess, we must…
-
comment
Comment #14205267
i think you're 'quite obviously' wrong ;).
-
comment
Comment #14205200
you conveniently forgot to mention the fundamental difference: the upstream kernel isn't developed for free whereas our code has always been. changes the equation quite a bit, does…