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: <CALCETrVcE6-XJSsV2wW=dyjpC1=Gx9ogFXx3s96=uEQMARTf_w@mail.gmail.com>
Date:	Tue, 1 Sep 2015 14:40:35 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Josh Boyer <jwboyer@...oraproject.org>
Cc:	David Herrmann <dh.herrmann@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: Re: kdbus_proc_permission (Re: [GIT PULL] kdbus updates for Greg)

On Tue, Sep 1, 2015 at 2:24 PM, Josh Boyer <jwboyer@...oraproject.org> wrote:
>
> Confining things through xattr labels on inodes.  ;)  FWIW, despite
> warnings to the contrary, the test system I have does boot just fine
> with SELinux in Enforcing mode.  It is likely the least scientific and
> useful scenario though, as it is just a dumb headless NUC box that all
> I do is test kernels on.  I won't even pretend that my mention here is
> anything more than an anecdote along the lines of "cool story, bro."

It's too bad that there isn't a well-supported way to lock down /proc
other than setting up inode labels and adding MAC policy.

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ