On Mon, May 28, 2012 at 01:13:15PM +0200, Andreas Henriksson wrote: > Hello again! > > I'm reopening this bug report again, since the just uploaded > iproute 20120521-2 has disabled the hardening build flags > because of multiple breakages. Two have been identified, > who knows how many more there are.... See: #674730, #674847 > (A proper testsuite for iproute2 would be really awesome > and very helpful here!) > > In my point of view, more investigation is needed to make > sure iproute2 is possible to harden without crippling > it's functionality. > Changes might be needed, which should happen in collaboration > with upstream. > > Unfortunately the time I have to spend on this limits me to > mostly trivial fixes. I don't think I'll be able to work > on this, so help is needed if this is going to happen. > > I have a good relation to upstream and can assist in > establishing contact and guide interested people in how to > work with upstream if you are new to kernel style > development practices.
These links have some hints how to usually enable hardening: http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough I don't know if iproute is special case that is incompatible. gcc-4.7 (default with amd64 and i386) has some fixes for code generation in versions 4.7.0-11 and 4.7.0-12 (released after iproute hardening compile) So it may be worth trying again with newer compiler (or forcing gcc-4.6). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
