Bug#651481: provide external interface to query expected hardening features

2011-12-29 Thread Raphael Hertzog
On Wed, 28 Dec 2011, Kees Cook wrote: > Adjusted. Refreshed patches attached... I just merged them with a few tweaks: - some rewording of the commit short descriptions - some small style adjustments > +sub set_feature { > +my ($self, $area, $feature, $enabled) = @_; > +$self->{features}->

Bug#651481: provide external interface to query expected hardening features

2011-12-28 Thread Kees Cook
On Thu, Dec 29, 2011 at 04:14:47AM +0100, Guillem Jover wrote: > On Wed, 2011-12-28 at 15:28:45 -0800, Kees Cook wrote: > > On Sun, Dec 18, 2011 at 09:42:50AM +0100, Guillem Jover wrote: > > > On Fri, 2011-12-16 at 16:39:25 -0800, Kees Cook wrote: > > > > Fresh patch attached! :) > > > > > > Thank

Bug#651481: provide external interface to query expected hardening features

2011-12-28 Thread Guillem Jover
On Wed, 2011-12-28 at 15:28:45 -0800, Kees Cook wrote: > On Sun, Dec 18, 2011 at 09:42:50AM +0100, Guillem Jover wrote: > > On Fri, 2011-12-16 at 16:39:25 -0800, Kees Cook wrote: > > > Fresh patch attached! :) > > > > Thanks! Could you split the refactoring/cleaning into its own patch > > (actuall

Bug#651481: provide external interface to query expected hardening features

2011-12-28 Thread Kees Cook
Hi Guillem, On Sun, Dec 18, 2011 at 09:42:50AM +0100, Guillem Jover wrote: > On Fri, 2011-12-16 at 16:39:25 -0800, Kees Cook wrote: > > Fresh patch attached! :) > > Thanks! Could you split the refactoring/cleaning into its own patch > (actually something that already crossed my mind when first se

Bug#651481: provide external interface to query expected hardening features

2011-12-18 Thread Guillem Jover
Hi! On Fri, 2011-12-16 at 16:39:25 -0800, Kees Cook wrote: > Fresh patch attached! :) Thanks! Could you split the refactoring/cleaning into its own patch (actually something that already crossed my mind when first seeing the original buildflags code), and the new functionality into another one?

Bug#651481: provide external interface to query expected hardening features

2011-12-16 Thread Kees Cook
On Fri, Dec 16, 2011 at 09:25:10AM +0100, Raphael Hertzog wrote: > On Thu, 15 Dec 2011, Kees Cook wrote: > > While doing this, it seemed that creating a full "set_feature()" callback > > was more work than it needed to be. I can certainly add it, but I thought > > I'd show you where I am now first.

Bug#651481: provide external interface to query expected hardening features

2011-12-16 Thread Raphael Hertzog
Hi, On Thu, 15 Dec 2011, Kees Cook wrote: > > $flags->{'features'}{'hardening'} is mostly the same than %use_feature, > > please do not duplicate it but rather modify the code so that it works > > that way: > > 1/ generate %use_feature by directly taking into account the architecture > >specif

Bug#651481: provide external interface to query expected hardening features

2011-12-15 Thread Kees Cook
Hi Raphael, On Fri, Dec 09, 2011 at 12:02:21PM +0100, Raphael Hertzog wrote: > On Thu, 08 Dec 2011, Kees Cook wrote: > > This patch adds that ability, and lets the environment correctly adjust it: > > > > $ dpkg-buildflags --features hardening > > -bindnow,+format,+fortify,-pie,+relro,+stackprote

Bug#651481: provide external interface to query expected hardening features

2011-12-09 Thread Raphael Hertzog
On Thu, 08 Dec 2011, Kees Cook wrote: > This patch adds that ability, and lets the environment correctly adjust it: > > $ dpkg-buildflags --features hardening > -bindnow,+format,+fortify,-pie,+relro,+stackprotector > > $ DEB_HOST_ARCH=ia64 dpkg-buildflags --features hardening > -bindnow,+format,+

Bug#651481: provide external interface to query expected hardening features

2011-12-08 Thread Kees Cook
Package: dpkg Version: 1.16.1.2 Severity: normal Tags: patch Hi, In working through the requirements for adding hardening build checks to lintian[1], it has become clear that there needs to be a way to ask dpkg-buildflags what its expected features area for a given situation. This patch adds tha