[DSE-Dev] CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE

[Ben Hutchings]

On Sun, 2017-04-02 at 16:43 +0200, cgzones wrote:
> On 2 Apr 2017 3:47 pm, "Ben Hutchings" <ben at decadent.org.uk> wrote:
> > 
> > On Sun, 2017-04-02 at 14:35 +0200, Laurent Bigonville wrote:
> > > Le 02/04/17 à 03:25, cgzones a écrit :
> > > > Is there any reason why the standard Debian kernel sets the value for
> > > > checkreqprot to 1, while the default[1] is 0?
> > 
> > The default is 1.  The commit changing the default to 0 went into
> > 4.11-rc4, i.e. it is not even in an upstream stable release yet.
> 
> 
> The change is from Okt 15, 4.4-rc1
[...]

You're right; I was confused by the Github web view that you linked to.
(Does anyone know why it shows the latest tag as well as the earliest
tag containing the commit?)

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof because fools are so
ingenious.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/selinux-devel/attachments/20170402/42852af5/attachment-0001.sig>