You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Stack Smashing Protection for Debian:

#5 Re: Stack Smashing Protection for Debian Posted by Anonymous (81.57.xx.xx) on Sun 25 Jun 2006 at 12:07 Well, there's no much risk for this to become a release blocker: - The gcc option can be inhibited for any problematic package (at the end of the day, any possible bug introduced in a package by SPP can be fixed with a one-liner in debian/rules - no long standing RC bugs). - Being on by default in Fedora Core 5, most packages (and at least, the vital ones) had been tested with SPP. Also, Debian-Hardened, Gentoo-Hardened and OpenBSD had cleaned the road for us with propolice. The later (OpenBSD) runs on about the same hardware architectures than Debian. - If for whatever reason things goes too bad, removing this default behaviour would only imply recompiling the packages. It's not like the protected packages would become dependant of a functionality. - If it has to be widely tested, it's the time to do it: before the (planned soon) toolchain freeze. Furthermore activating it require recompiling the archive, that's inconvenient for most developpers if they need to do it by themself: it won't be intensivly tested unless activated on the archive. I hardly can see any dramatic effect of activating this by default, even if bugs raises on.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account