From: "Paul Moore" <paul.moore@hp.com>
To: <jmorris@namei.org>
Cc: <michal.k.k.piotrowski@gmail.com>,
<torvalds@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<sds@tycho.nsa.gov>
Subject: Re: [GIT] SELinux changes for 2.6.23 (updated)
Date: 13 Jul 2007 06:41:00 -0400 [thread overview]
Message-ID: <3267153665.17485311@mail.hp.com> (raw)
-----Original Message-----
From: James Morris <jmorris@namei.org>
Date: Thursday, Jul 12, 2007 10:50 pm
Subject: Re: [GIT] SELinux changes for 2.6.23 (updated)
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
CC: Linus Torvalds <torvalds@linux-foundation.org>, linux-kernel@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>, Paul Moore <paul.moore@hp.com>
On Fri, 13 Jul 2007, Michal Piotrowski wrote:
>
>>
> My system is too secure, I can not login :)
>
>Do you have CONFIG_NETLABEL=y ?
>
>If so, please try disabling it.
Disabling NetLabel should solve the problem. The recommended solution to this problem, as discussed on the SELinux list and mentioned in the patch description, is to upgrade your SELinux policy to the latest Reference Policy sources. For those with custom SELinux policy, the patch description explains the changes to the SELinux policy required.
If needed I can post more instructions later, let me know, but right now I'm tapping this out on my phone while at the airport.
. paul moore
. linux security @ hp
next reply other threads:[~2007-07-13 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 10:41 Paul Moore [this message]
2007-07-13 19:08 ` The art of breaking userspace (was Re: [GIT] SELinux changes for 2.6.23 (updated)) Michal Piotrowski
2007-07-13 19:29 ` Stephen Smalley
2007-07-14 3:20 ` Paul Moore
-- strict thread matches above, loose matches on Subject: below --
2007-07-12 3:20 [GIT] SELinux changes for 2.6.23 (updated) James Morris
2007-07-12 23:39 ` Michal Piotrowski
2007-07-13 2:49 ` James Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3267153665.17485311@mail.hp.com \
--to=paul.moore@hp.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=sds@tycho.nsa.gov \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox