linux-kernel - Re: [PATCH V3] security/selinux: Always allow FIOCLEX and FIONCLEX

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]

Date:   Fri, 25 Feb 2022 15:54:46 -0500
From:   Paul Moore <paul@...l-moore.com>
To:     Ondrej Mosnacek <omosnace@...hat.com>
Cc:     Richard Haines <richard_c_haines@...nternet.com>,
        SElinux list <selinux@...r.kernel.org>,
        Stephen Smalley <stephen.smalley.work@...il.com>,
        Eric Paris <eparis@...isplace.org>, demiobenour@...il.com,
        Linux kernel mailing list <linux-kernel@...r.kernel.org>,
        selinux-refpolicy@...r.kernel.org,
        Jeff Vander Stoep <jeffv@...gle.com>
Subject: Re: [PATCH V3] security/selinux: Always allow FIOCLEX and FIONCLEX

On Fri, Feb 25, 2022 at 5:02 AM Ondrej Mosnacek <omosnace@...hat.com> wrote:
> (IMHO the POLICYDB_CAPABILITY_ prefix is ridiculously long for no
> reason and we should simply shorten it (just POLCAP_ would be
> perfectly fine, IMHO) instead of trying to abbreviate the rest. Of
> course, this doesn't have to be done now - I'm taking a note to myself
> to splice in such rename next time I add a new capability, if not
> earlier.)

Yeah, that prefix is probably longer than it needs to be.  Since we're
at -rc5 right now, with -rc6 just a few days away, I'll go ahead and
toss out a patch to shorten the names next week.  While I have very
mixed feelings on style/formatting-only patches, things like this
should go into selinux/next at the end of the -rcX cycle so as not to
cause unnecessary conflicts for people making "real" changes :)

-- 
paul-moore.com