From: Tom <tom@lemuria.org>
To: SELinux@tycho.nsa.gov
Subject: Re: db conflict ?
Date: Fri, 12 Apr 2002 17:01:31 +0200 [thread overview]
Message-ID: <20020412170130.A30042@lemuria.org> (raw)
In-Reply-To: <20020412161729.B29624@lemuria.org>; from tom@lemuria.org on Fri, Apr 12, 2002 at 04:17:29PM +0200
On Fri, Apr 12, 2002 at 04:17:29PM +0200, Tom wrote:
> It looks like I solved the problem, at least it now boots and appears
> to run fine, except that I can't log in remotely, but ssh localhost
> works. I'll inspect that later.
Funny thing, I guess I found the revers of "NoRootLogin" :)
Analysis: Logging in via ssh as root works, as a user not. i.e. "ssh
-l tom testmachine" fails, "ssh -l root testmachine" works.
The error message in /var/log/auth.log is:
fatal: Could not obtain SID for user tom
The piece of code that triggers this appears to be:
if (!get_default_user_sid(pw->pw_name,
strlen(pw->pw_name),
&scontext,
&sid)) {
fprintf(stderr, "Could not obtain SID for user %s\n",
pw->pw_name);
exit(1);
}
so I wonder why this fails, because my /etc/selinux/users says:
user user_u roles user_r;
user root roles { user_r sysadm_r };
user tom roles { user_r sysadm_r };
so tom should be more than covered. or am I just being dumb again?
--
http://web.lemuria.org/pubkey.html
pub 1024D/D88D35A6 2001-11-14 Tom Vogt <tom@lemuria.org>
Key fingerprint = 276B B7BB E4D8 FCCE DB8F F965 310B 811A D88D 35A6
--
You have received this message because you are subscribed to the selinux 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:[~2002-04-12 15:01 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 10:23 db conflict ? Tom
2002-04-12 12:05 ` Russell Coker
2002-04-12 13:01 ` Tom
2002-04-12 14:07 ` Russell Coker
2002-04-12 14:40 ` Stephen Smalley
2002-04-12 15:15 ` Russell Coker
2002-04-12 19:03 ` [patch] " Stephen Smalley
2002-04-12 13:09 ` Stephen Smalley
2002-04-12 13:27 ` Russell Coker
2002-04-12 13:06 ` Stephen Smalley
2002-04-12 13:58 ` Russell Coker
2002-04-12 14:07 ` Stephen Smalley
2002-04-12 14:38 ` Russell Coker
2002-04-12 14:48 ` Stephen Smalley
2002-04-12 15:12 ` Russell Coker
2002-04-12 17:01 ` Howard Holm
2002-04-12 17:09 ` Russell Coker
2002-04-12 17:13 ` Stephen Smalley
2002-04-12 14:17 ` Tom
2002-04-12 14:21 ` Stephen Smalley
2002-04-12 14:34 ` Russell Coker
2002-04-12 14:50 ` Tom
2002-04-12 15:01 ` Tom [this message]
2002-04-12 15:11 ` Stephen Smalley
2002-04-12 15:15 ` Tom
2002-04-12 15:29 ` Tom
2002-04-12 16:35 ` Stephen Smalley
2002-04-12 16:50 ` Tom
2002-04-12 17:04 ` Stephen Smalley
2002-04-12 17:40 ` Tom
2002-04-12 17:49 ` Stephen Smalley
2002-04-12 16:33 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 17:26 Westerman, Mark
2002-04-12 17:29 ` Stephen Smalley
2002-04-12 17:37 Westerman, Mark
2002-04-12 18:03 ` Russell Coker
2002-04-12 19:17 ` Stephen Smalley
2002-04-12 20:11 ` Russell Coker
2002-04-12 20:25 ` Howard Holm
2002-04-12 21:01 ` Russell Coker
2002-04-15 14:44 ` Howard Holm
2002-04-12 20:18 ` Howard Holm
2002-04-15 16:08 ` Dale Amon
2002-04-18 14:54 ` Stephen Smalley
2002-04-18 15:42 ` Russell Coker
2002-04-19 20:20 ` Stephen Smalley
2002-04-12 17:45 Westerman, Mark
2002-04-12 18:12 ` Stephen Smalley
2002-04-12 18:13 Westerman, Mark
2002-04-12 19:42 ` Russell Coker
2002-04-12 20:33 Westerman, Mark
2002-04-15 14:40 ` Howard Holm
2002-04-15 15:16 Westerman, Mark
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=20020412170130.A30042@lemuria.org \
--to=tom@lemuria.org \
--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.