Talk:Buffer overflow protection

message: "Gentoo Linux uses ProPolice according to gcc -v:" Wouldnt that be better put as "Gentoo will use the ssp patch for gcc by default" Since gentoo's packages arent binarys. Stack-Smashing_Protector puts it in a better way --2mcm 21:43, 3 May 2005 (UTC)
thread_title: Gentoo and ProPolice

message: It looks fine to me. Graue 15:27, 23 May 2005 (UTC)
thread_title:  Why is this marked as in need of cleanup? 

message: There are description of several FOSS implementations but nothing about the /GS (guardstack) option of microsoft compilers, I think it would be a worthy addition. Trou 21:39, 22 May 2007 (UTC)
thread_title:  what about /GS ? 

message: The revision of 20:42, 3 August 2005 changed the value 13 to 3 with a justification that does not apply to the example. The example shows that there are 13 bytes from the address of "d" to the address of the "b". More than 3 but fewer than 13 written to "d" will corrupt "c" without overwriting the pointer "b".  I changed this back to 13. 142.16.23.254 00:33, 11 August 2007 (UTC)
replies: text: Someone else made this change in 2010. Putting it back... .froth. (talk) 04:35, 17 January 2012 (UTC)
thread_title:  example of canary 

message: the cited immunix paper  is hardly spam.  immunix was a DARPA-funded research project which produced the original stackguard.  other benchmark sources: , 
Tfinn 03:02, 17 August 2007 (UTC)
thread_title:  reference to immunix paper is spam? 

message: I came to this article via the redirect guard page (found under sprintf). This article here currently does not explain what a guard page is. Can someone explain? Thanks, --Abdull (talk) 13:53, 10 March 2010 (UTC)
thread_title:  Guard page? 

message: Everything in this article only refers stack protection, not to buffer overflow protection in general. I think this article should be renamed to "stack protection" or maybe even "stack-smashing protection", because that's the common parlance in GCC circles. Opinions? MalcolmInglis (talk) 09:58, 27 September 2013 (UTC)
replies: text: If renamed, I would advocate "stack overflow protection", though "stack smashing protection" would also be okay. However, I think the thing to do would be to rework the article. The section on compiler flags and stuff is specific to preventing stack smashing attacks, but the general idea is more broadly applicable. I think some heap allocators put canaries between blocks, and there are hardening systems that will put them within objects and between buffers, as well as others that will use more powerful guards to protect against over*reads*, which aren't hindered at all by canaries as described by the current article version. These have varying tradeoffs between implementation simplicity, added security, and performance overhead of course. Point being: except for the compilers discussion, only the presentation is *really* stack-specific. I might take a shot at reworking things at some point. 66.188.116.58 (talk) 15:44, 6 February 2015 (UTC)
replies: text: I think "buffer overflow protection" is the more common term, and including heap overflows here is a good idea, unless we want another article on that.  But the intro really needs a work-over to avoid redundancy and include the distinction between heaps and stacks etc more naturally.  ★NealMcB★ (talk) 12:40, 20 July 2016 (UTC)
thread_title:  Rename article to "stack protection"? 

message: Hello fellow Wikipedians,
I have just modified  on Buffer overflow protection. 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/20130309083252/http://tmp-www.cpe.ku.ac.th/~mcs/courses/2005_02/214573/papers/buffer_overflows.pdf to http://tmp-www.cpe.ku.ac.th/~mcs/courses/2005_02/214573/papers/buffer_overflows.pdf
*Corrected formatting/usage for http://www.linux.org.uk/~ajh/gcc/gccsummit-2003-proceedings.pdf
*Added archive https://web.archive.org/web/20081015082745/http://www.phrack.org:80/issues.html?issue=49&id=14 to http://www.phrack.org/issues.html?id=14&issue=49
*Added archive https://web.archive.org/web/20070204050551/http://www.paranoid.nl:80/%7Eeilander/freebsd/propolice/ to http://www.paranoid.nl/~eilander/freebsd/propolice/
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 10:48, 10 November 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on Buffer overflow protection. 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/20040715225038/http://www.linux.org.uk/~ajh/gcc/gccsummit-2003-proceedings.pdf to http://www.linux.org.uk/~ajh/gcc/gccsummit-2003-proceedings.pdf
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:05, 14 December 2017 (UTC)
thread_title:  External links modified