All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Dennis Wronka <linuxweb@gmx.net>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: can't login in enforcing mode for some reason.
Date: Sat, 05 Sep 2009 00:52:47 -0700	[thread overview]
Message-ID: <4AA218CF.9040601@gmail.com> (raw)
In-Reply-To: <200909051515.20822.linuxweb@gmx.net>

I think I got it, looking at the inittab from
clfs
they have:

|1:2345:respawn:/sbin/agetty -I '\033(K' tty1 9600|

and from lfs its:|

1:2345:respawn:/sbin/agetty tty1 9600|

maybe the|  -I '\033(K' was causing issues.
once I loaded the regular lfs inittab the
policy loaded as it should as well as system_u:system_r:local_login_t
for the login.

Thanks for the info, if it wasn't for you I wouldn't have looked
in inittab.
|
:^)


Dennis Wronka wrote:
> Is that on a regular distro or on your custom compile?
>
> If the latter: Which getty are you using? I had serious problems with agetty,
> but could get around those by switching to mingetty.
>
> Also I think there are two version of login, the one you're using may depend
> on the compile-order. I think one is in the shadow-package and one is in util-
> linux-ng. For a reason that I don't remember I think I am now using the one in
> util-linux-ng.
>
>    


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      parent reply	other threads:[~2009-09-05  7:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05  5:30 can't login in enforcing mode for some reason Justin Mattock
2009-09-05  5:57 ` Justin P. Mattock
2009-09-05  7:15 ` Dennis Wronka
2009-09-05  7:34   ` Justin P. Mattock
2009-09-05  7:51     ` Dennis Wronka
2009-09-05  7:52   ` Justin P. Mattock [this message]

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=4AA218CF.9040601@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linuxweb@gmx.net \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.