All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: "c.r.madhusudhanan@gmail.com" <c.r.madhusudhanan@gmail.com>,
	selinux@tycho.nsa.gov
Subject: Re: Regarding SELinux User mapping
Date: Sat, 28 May 2011 08:45:15 +1000	[thread overview]
Message-ID: <201105280845.15665.russell@coker.com.au> (raw)
In-Reply-To: <BANLkTik7AS=9J4gXUpORehuEAJxYcizQXA@mail.gmail.com>

On Fri, 27 May 2011, "c.r.madhusudhanan@gmail.com" 
<c.r.madhusudhanan@gmail.com> wrote:
> Thanks for the quick response. Meego doesnt use pam_selinux by default.
> 
> I will try to enable the pam_selinux support, and let you know the result.
> Thanks for the help.

In the early days we had SE Linux patches for all login programs, pam_selinux 
is a more recent development.  You should be able to find the old login 
patches somewhere, although given the evolution of APIs it might be better to 
take the pam_selinux code and develop your own login patch.

PAM isn't required for SE Linux support (or anything really), it's just a lot 
easier in most cases.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

--
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:[~2011-05-27 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 12:50 Regarding SELinux User mapping c.r.madhusudhanan
2011-05-27 13:00 ` Stephen Smalley
2011-05-27 13:01 ` Dominick Grift
2011-05-27 13:30   ` c.r.madhusudhanan
2011-05-27 15:09     ` c.r.madhusudhanan
2011-05-27 22:45     ` Russell Coker [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=201105280845.15665.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=c.r.madhusudhanan@gmail.com \
    --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.