Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #57424
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE |
| Date | 2017-04-02 21:30 +0200 |
| Message-ID | <trTmh-4Gv-7@gated-at.bofh.it> (permalink) |
| References | (7 earlier) <trN7b-w5-19@gated-at.bofh.it> <trN7b-w5-21@gated-at.bofh.it> <trN7b-w5-5@gated-at.bofh.it> <trO3f-16F-13@gated-at.bofh.it> <trOZj-1KM-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sun, 2017-04-02 at 16:43 +0200, cgzones wrote: > On 2 Apr 2017 3:47 pm, "Ben Hutchings" <ben@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.
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Laurent Bigonville <bigon@debian.org> - 2017-04-02 14:50 +0200
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Ben Hutchings <ben@decadent.org.uk> - 2017-04-02 15:50 +0200
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE cgzones <cgzones@googlemail.com> - 2017-04-02 16:50 +0200
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Ben Hutchings <ben@decadent.org.uk> - 2017-04-02 21:30 +0200
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Christian Göttsche <cgzones@googlemail.com> - 2017-04-11 17:00 +0200
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Laurent Bigonville <bigon@debian.org> - 2017-04-11 17:20 +0200
Re: CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Ben Hutchings <ben@decadent.org.uk> - 2017-04-11 21:40 +0200
Re: [DSE-Dev] CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE Russell Coker <russell@coker.com.au> - 2017-04-02 17:50 +0200
csiph-web