linux-kernel - RE: [PATCH] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <23e35a8fc78e414c982ab40670157667@AcuMS.aculab.com>
Date:   Tue, 8 Feb 2022 23:44:43 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Dominick Grift' <dominick.grift@...ensec.nl>,
        Chris PeBenito <chpebeni@...ux.microsoft.com>
CC:     William Roberts <bill.c.roberts@...il.com>,
        Paul Moore <paul@...l-moore.com>,
        Demi Marie Obenour <demiobenour@...il.com>,
        "Stephen Smalley" <stephen.smalley.work@...il.com>,
        Eric Paris <eparis@...isplace.org>,
        SElinux list <selinux@...r.kernel.org>,
        "Linux kernel mailing list" <linux-kernel@...r.kernel.org>,
        "selinux-refpolicy@...r.kernel.org" 
        <selinux-refpolicy@...r.kernel.org>
Subject: RE: [PATCH] SELinux: Always allow FIOCLEX and FIONCLEX

From: Dominick Grift
> Sent: 08 February 2022 16:47
...
> I would not mind removing these two checks, but i am not a big user of
> xperms (i only filter TIOSCTI on terminal chr files and only for the
> entities that write or append them).

TIOSCTI isn't your only problem.
Much 'fun' can be had with terminals that support a settable
answerback message.
Possibly that is limited to physical serial terminals, but some
emulators might be 'good enough' to support the relevant escape
sequences.

Even the default answerback message can be very confusing.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)