From: Jaspreet Singh <jsingh@ensim.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
nsa <SELinux@tycho.nsa.gov>
Subject: Re: pam_selinux when selinux is disabled
Date: Wed, 29 Dec 2004 17:14:14 +0530 [thread overview]
Message-ID: <1104320654.3805.10.camel@jsingh> (raw)
In-Reply-To: <1104265628.21391.152.camel@moss-spartans.epoch.ncsc.mil>
Hi,
On Tue, 2004-12-28 at 15:27 -0500, Stephen Smalley wrote:
> BTW, sshd is no longer using pam_selinux; we had to go back to a direct
> patch due to changes in the upstream sshd.
I am not storing my username/password in standard /etc/passwd but in
different files/DB.. so i have personalized getpwnam by
editing /etc/nsswitch.conf
thats works fine.
when you define users in a policy .. it calls python getpwnam and adds
user to selinux user db. So I guess even that is fine.
now .. the question is when login sets selinux context for a user which
system call it makes to get user identification and which system call it
uses to set the context.
If sshd is not relying on pam_selinux than .. is all this hard-coded in
sshd ???
Please clarify it.
Jaspreet.
--
--
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.
next prev parent reply other threads:[~2004-12-29 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 20:20 pam_selinux when selinux is disabled Luke Kenneth Casson Leighton
2004-12-28 20:15 ` Stephen Smalley
2004-12-28 20:27 ` Stephen Smalley
2004-12-29 11:44 ` Jaspreet Singh [this message]
2004-12-29 15:32 ` Daniel J Walsh
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=1104320654.3805.10.camel@jsingh \
--to=jsingh@ensim.com \
--cc=SELinux@tycho.nsa.gov \
--cc=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
/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.