Talk:PaX

message: It should be noted that PaX breaks a lot of applications that try to manage their own heap, i.e. by using a garbage collector. Notable examples include SBCL and CMUCL which try to setup a heap layout that conflicts with address space randomization of PaX. The funny thing is that PaX is completely worthless for these Lisp compilers, as it is practically not possible to produce buffer or integer overflows.  --Boelthorn 22:55, 18 July 2006 (UTC)
thread_title:  PaX bad for non-C programs 

message: "PaX at the time of this writing is not in the mainline kernel because The PaX Team does not wish to advocate it for mainline inclusion at this time."
... not to mention that, in the wake of the recent unpleasantness, the chances of Torvalds accepting an anonymous patch are zero? That was the very first thing that sprang to my mind when I saw the authors were playing anonymity games. I mean, wtf? Why the anonymity? There's going to be something relevant to discuss there. This is not normal practice, at all - David Gerard 06:46, 15 Jul 2004 (UTC)
thread_title: Anon author; not good?

message: Blue, I got some time sort of free and went through the first couple of sections doing clarity edits. I trust I haven't so grossly misunderstood something that I've lost meaning. And I hope that clarity has been increased; some unfelicities of language are at least corrected. The cost (aside from time) is some additional verbiage giving some of the background the less than expert might find useful. Tell me what you think. ww 19:14, 21 Jul 2004 (UTC)
thread_title: clarity edits

message: Pretty good.  You've been helpful :)  Though, you or the other editors have added factual and grammerical errors, or misleading statements; whoever said "no data is lost" is FLAT WRONG, because you can't save application data in the middle of a PaX kill ;)   But the stuff is salvagable and mouldable into a better form than before :)
I guess I"ll have to give this a hard re-read later and clean up :)
--John Moser 16:12, 22 Jul 2004 (UTC)
thread_title:  Needs work ;) 

message: ; please ensure that comments and changes are entered at Wikipedia featured article candidates, it is not sufficient to do so only here.
From the FAC:
 === PaX (Linux) ===
Contested -- July 13
self-nomination
PaX is an article about a security patch for Linux.  I enjoy using PaX, and wished to show my support by writing an article on it.  As the article is well written, and work that I am particularly proud of, I felt I could nominate PaX for FA.
The article is very accurate, as I've written most of it from my experience and from data I've read on PaX, and have had the developer run over it for me to make sure there were no factual issues.
Even though I am a hardcore PaX supporter, I leave my personal feelings about PaX out of the article.  I believe that I can best support PaX and the diffusion of information about it by avoiding any propagandist slur or influence in the article itself.  My goals are to present a complete and concise description of what PaX is and what it does, and I believe that I have achieved this in PaX.
I believe that the article is written in such a way that it only presents the user with complete and concise information about what PaX is and what it does, and leaves him with only deep technical questions which can be answered by visiting the PaX homepage--linked to in PaX--and reading through the several pages of technical documentation.  This is exactly what an encyclopedia is supposed to do.
--Bluefox Phoenix Lucid 04:10, 14 Jul 2004 (UTC)
thread_title: copied from featured article cand comments 

message: jm, References in the article to system calls or library calls might be well if they were set off typographically. I suggest that they be put into a monospaced typeface, which is a sort of standard for executable code in the book design world. I understand this will be a bit of work, but with an article of this technical nature, everything that can help the reader's mind get around the material is worthwhile. In fact, that's the writer's burden regardless of the article. Anyway, I thought I pass on the thought. ww 13:34, 23 Jul 2004 (UTC)
thread_title: suggested dab improvement

message: Sure, how do you do monospacing?
Also, nice with the clarity; although I need to keep up behind you for things that you keep getting wrong or making bad grammar out of :p  It's really helpful despite the rough edges though.
--John Moser 01:25, 25 Jul 2004 (UTC)
replies: text: jm, Sorry about errors. I've been trying for conceptual clarity not absolute precision, as is evident.  As for grammar, I trust (fervently hope, really) that they're typos. As for monospacing, it's something like (from memory now...) </small> stuff </small>. A look at one of the programming examples (eg, sort algorithms) will betray the trick exactly. ww 19:12, 26 Jul 2004 (UTC)
thread_title:  Monospacing 

message: This page is now a Featured Article!
Special thanks go to all of those who objected at the first FAC run and those who contributed, including Matt Crypto, Raul654, Ww, Taxman, Kate, Goplat, Timwi, David Gerard, and the rest of you who helped that I may have missed.  Although I undertook getting this article up to FA status as a personal goal, it could not have been done without the input, clarity, simplification, and spell checking of the Wikipedia community.
Special thanks also goes to The PaX Team for looking over the article and checking for accuracy several times.  It should be noted that there hasn't been an examination by them since the last bits of deep technical information were added (although the changes since then are supported by the information already gathered, or are not strongly technical); if something turns out to be inaccurate-- which should not be the case, but we are all human-- the fault would not lay on them.  :)
Again, thanks to you all for your contributions; now I don't have to spend 10 hours explaining PaX to newbies :D
--John Moser 06:31, 11 Aug 2004 (UTC)
thread_title:  Featured Article!!! :D 

message: During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!
* http://lists.netsys.com/pipermail/full-disclosure/2005-March/032240.html
** In PaX on Mon Jul 17 14:41:55 2006, Socket Error: (110, 'Connection timed out')
** In PaX on Thu Jul 27 00:36:42 2006, Socket Error: (110, 'Connection timed out')
----maru   (talk)  contribs 04:36, 27 July 2006 (UTC)
thread_title:  Dead link 

message: PaX#Randomized mmap() base says On 32-bit systems, this amounts to 16 orders of magnitude; that is, the chances of success are recursively halved 16 times.. If an amount is halved 16 times it gets 2^16 = 65536 times smaller, which is 5 orders of magnitude, not 16. Orders of magnitude states that sometimes powers of 2 are used instead of powers of 10, but that's so uncommon that in my opinion "65536 times" should be used instead. // Duccio (write me) 23:01, 24 August 2006 (UTC)
thread_title:  Orders of magnitude 

message: Hopefully Portal:Free_software can attract some people here to help improve the article so that it doesn't lose its featured article status.  For one thing, I recommend that people add references to this article. It will remain on the portal for a week or so. The previous selected article was Emacs. Gronky 23:02, 11 June 2007 (UTC)
replies: text: Well, I can't say it helped much.  Anyway, the selected article has moved on again and is now OpenWrt. Gronky 15:39, 20 June 2007 (UTC)
thread_title:  On [[Portal:Free software]], PaX is currently the selected article 

message: Am I right to think that PaX's executable space protection is analogous to Windows SP2 and later's data execution prevention feature?  Would it be relevant to mention this in the article? RW 02:57, 9 July 2007 (UTC)
thread_title:  Data execution prevention 

message: This article's only reference is the documentation of the subject, with no inline citations. Is anyone interested enough in this article to improve it to the current featured article standard? Pagrashtak 01:06, 27 October 2007 (UTC)
thread_title:  Needs references 

message: On the Effectiveness of Address-Space Randomization demonstrates an attack on PaX ASLR from 2004 that requires brute forcing 16 bits (with an upper bound of 20 bits) of randomness for systems with 32-bit address spaces. Probably worth a mention in the article, but I don't know how future work on it turned out.
Swolchok (talk) 22:22, 27 January 2009 (UTC)
thread_title:  Attack against PaX requiring brute forcing only 16 bits (up to 20 maximum) 

message: Hello fellow Wikipedians,
I have just added archive links to  on PaX. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive http://web.archive.org/web/20070926222018/http://packetstorm.linuxsecurity.com/0503-exploits/paxomatic.c to http://packetstorm.linuxsecurity.com/0503-exploits/paxomatic.c
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 14:25, 28 February 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on PaX. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20070928120508/http://fist.immunitysec.com/pipermail/dailydave/2005-March/001619.html to http://fist.immunitysec.com/pipermail/dailydave/2005-March/001619.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 14:41, 20 May 2017 (UTC)
thread_title:  External links modified 

message: As grsecurity was deleted too, is this single patch from that patchset any more notable than the patchset itself? --ilmaisin (talk) 22:57, 19 August 2021 (UTC)
thread_title:  Notability?