linux-kernel - Re: [GIT PULL] SELinux patches for v4.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHC9VhQL6CL9bk_HNfUr+4RyNvmTC=Qn3NkPV8xk+rbjFOhNgA@mail.gmail.com>
Date:   Tue, 12 Sep 2017 18:00:29 -0400
From:   Paul Moore <paul@...l-moore.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     James Morris <jmorris@...ei.org>, selinux@...ho.nsa.gov,
        LSM List <linux-security-module@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] SELinux patches for v4.14

On Tue, Sep 12, 2017 at 4:24 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Tue, Sep 12, 2017 at 10:33 AM, Paul Moore <paul@...l-moore.com> wrote:
>> As discussed on the linux-security pull request thread, this is the
>> direct SELinux pull request; the content/tag is the same as what I
>> sent to James/linux-security earlier:
>
> The contents may be the same, but the base is different.
>
> In particular, you based it on the security tree that already had a
> few other patches, so now that branch contains not just selinux work,
> but also a couple of tomoyo patches that came in that way.
>
> Anyway, I pulled this simply because it was easier to review and
> didn't have anything I disliked per se, but if we're going to actually
> keep the different securlty layers separate, they need to also have
> clean bases for the work in the future.
>
> Anyway, I'm at the airport on my way back home, and hopefully I'll be
> back to normal tomorrow after a good night's sleep, and I can take a
> look at the rest.

Oof, sorry about the base mixup; I'll change the SELinux tree base
moving forward so this shouldn't happen again.

-- 
paul moore
www.paul-moore.com