All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "c.r.madhusudhanan@gmail.com" <c.r.madhusudhanan@gmail.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Wrong context for user
Date: Fri, 24 Jun 2011 08:53:50 -0400	[thread overview]
Message-ID: <4E0488DE.3000300@redhat.com> (raw)
In-Reply-To: <BANLkTinYGbMPaUMmJwMiCkxnBQEvZOd16g@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/24/2011 08:04 AM, c.r.madhusudhanan@gmail.com wrote:
> Hi All,
> 
> 
> I have meego configured with SELinux refpolicy. I have enabled SELinux
> user to linux user mapping, and though it shows correct selinux user and
> selinux role, 
> the domain/type appears to be wrong.
> 
> For example, when I login linux user "meego", and say ps -Z, it shows me,
> 
> user_u:user_r:insmod_t          773   tty1   00:00:00 bash
> user_u:user_r:insmod_t          795   tty1   00:00:00 ps
> 
> where I expect this has to be user_u:user_r:user_t, any pointers?
> 
> 
> Regards,
> Madhu
Most likely your login program is not running with the correct context.

ps -eZ | grep login
- --> Should be local_login_t
ps -eZ | grep sshd
- --> Should be sshd_t
ps -eZ | grep gdm
- --> Should be xdm_t

Usually login programs running as the wrong context need to be
relabeled.  touch /.autorelabel; reboot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk4EiN4ACgkQrlYvE4MpobMTewCg6FBaXsxZaJ/veVWbiqfeS38m
B2gAoM1iOR3Dd9fjoyDHM6NFDve09VB8
=Xrpt
-----END PGP SIGNATURE-----

--
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.

  reply	other threads:[~2011-06-24 12:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 12:04 Wrong context for user c.r.madhusudhanan
2011-06-24 12:53 ` Daniel J Walsh [this message]
2011-06-24 12:57 ` Stephen Smalley
2011-06-24 13:44   ` c.r.madhusudhanan
2011-06-24 13:55     ` Daniel J Walsh
2011-06-24 14:11     ` Stephen Smalley
2011-06-24 14:44       ` c.r.madhusudhanan
2011-06-24 14:48         ` Stephen Smalley
2011-06-24 14:52           ` c.r.madhusudhanan
2011-06-24 15:09             ` Stephen Smalley
2011-06-24 15:50               ` c.r.madhusudhanan
2011-06-24 21:26                 ` Sam Gandhi
2011-06-28 15:34                   ` c.r.madhusudhanan
2011-07-01 13:23                 ` Stephen Smalley
2011-07-01 13:50                   ` Stephen Smalley
2011-07-05 14:43                   ` c.r.madhusudhanan
2011-07-01 13:56         ` Stephen Smalley
2011-07-01 16:17           ` Stephen Smalley
2011-07-06 14:14           ` c.r.madhusudhanan

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=4E0488DE.3000300@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=c.r.madhusudhanan@gmail.com \
    /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.