Your message dated Sun, 6 Jan 2013 18:25:44 +0100 with message-id <[email protected]> and subject line Re: security.d.o: 342044: close this? has caused the Debian Bug report #342044, regarding security.debian.org: Systemically making Debian GNU/Linux less suseptible to buffer overflow attacks to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 342044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342044 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: security.debian.org Severity: wishlist I just read an article that talked about several ways to reduce the chance of a hacker taking advantage of a system due to buffer overflow attacks. Besides using Java, of course. They mentioned StackGuard, ProPolice, StackShield, and RAD (Return Address Defender) for the compiler and libsafe (already a Debian package in sid) for the OS. Some of these have been discussed on Debian lists already. I have no idea how these tools might be incorporated into Debian, but I think it would be a Good Thing if every program were protected by them. It would make our systems safer, and would be great for Debian marketing. The article is Detection and Prevention of Stack Buffer Overlow Attacks by Kuperman, Brodley, Ozdoganoglu, Vijaykumar, and Jalote, Communications of the ACM, November 2005, p. 51-56. A web page containing references can be found at: https://engineering.purdue.edu/ResearchGroups/SmashGuard/BoF.html -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (80, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) -- Bill Wohler <[email protected]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane.
--- End Message ---
--- Begin Message ---On Thu, Nov 22, 2012 at 03:32:51PM +0800, Paul Wise wrote: > Since the GCC maintainers decided not to enable hardening flags by > default and we have made some progress in manually adding the hardening > flags to each and every package, perhaps this bug should be closed? Ack. Cheers, Moritz
--- End Message ---
