linux-kernel - Re: [PATCH v3] selinux: measure state and policy capabilities

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 5 Mar 2021 11:29:47 -0800
From:   Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>
To:     Paul Moore <paul@...l-moore.com>,
        James Bottomley <James.Bottomley@...senpartnership.com>
Cc:     zohar@...ux.ibm.com,
        Stephen Smalley <stephen.smalley.work@...il.com>,
        tusharsu@...ux.microsoft.com, tyhicks@...ux.microsoft.com,
        casey@...aufler-ca.com, agk@...hat.com, snitzer@...hat.com,
        gmazyland@...il.com, sashal@...nel.org,
        James Morris <jmorris@...ei.org>,
        linux-integrity@...r.kernel.org, selinux@...r.kernel.org,
        linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] selinux: measure state and policy capabilities

On 3/5/21 11:22 AM, Paul Moore wrote:

Hi Paul,

> On Fri, Mar 5, 2021 at 12:57 PM James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
>> On Fri, 2021-03-05 at 12:52 -0500, Paul Moore wrote:
>> [...]
>>> This draft seems fine to me, but there is a small logistical blocker
>>> at the moment which means I can't merge this until -rc2 is released,
>>> which likely means this coming Monday.  The problem is that this
>>> patch relies on code that went upstream via in the last merge window
>>> via the IMA tree, not the SELinux tree; normally that wouldn't be a
>>> problem as I typically rebase the selinux/next to Linus' -rc1 tag
>>> once the merge window is closed, but in this particular case the -rc1
>>> tag is dangerously broken for some system configurations (the tag has
>>> since been renamed) so I'm not rebasing onto -rc1 this time around.
>>>
>>> Assuming that -rc2 fixes the swapfile/fs-corruption problem, early
>>> next week I'll rebase selinux/next to -rc2 and merge this patch.
>>> However, if the swapfile bug continues past -rc2 we can consider
>>> merging this via the IMA tree, but I'd assume not do that if possible
>>> due to merge conflict and testing reasons.
>>
>> If it helps, we rebased the SCSI tree on top of the merge for the
>> swapfile fix which is this one, without waiting for -rc2:
> 
> Considering that -rc2 is only two days away I'm not going to lose a
> lot of sleep over it.
> 

Thanks for reviewing the patch.

I can wait until the swapfile issue is resolved (in rc2 or later) and 
you are able to merge this patch. Please take your time.

thanks,
   -lakshmi