Re: pam_unix.so error and lock order reversal

2002-04-14 Thread Rasmus Skaarup



On Sat, 13 Apr 2002, Terry Lambert wrote:

 Rasmus Skaarup wrote:
  2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
  4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
  works fine. Is this somekind of security feature? :-)

 Pretty much.  The user it attempts to log you in as is still
 root, because that's still your identity, even if it's not
 your current credential.

[...]

 You might want to try using su - instead of su, in
 order to actually *become* the other person.

I am.


Best regards,
Rasmus Skaarup




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pam_unix.so error and lock order reversal

2002-04-14 Thread Terry Lambert

Rasmus Skaarup wrote:
 On Sat, 13 Apr 2002, Terry Lambert wrote:
  Rasmus Skaarup wrote:
   2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
   4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
   works fine. Is this somekind of security feature? :-)
 
  Pretty much.  The user it attempts to log you in as is still
  root, because that's still your identity, even if it's not
  your current credential.
 
 [...]
 
  You might want to try using su - instead of su, in
  order to actually *become* the other person.
 
 I am.

You might try ssh user@machinename instead of ssh machinename.

You might also try logging in as someone other than root (;^)).

Finally, you might want to remove ~root/.ssh, and let it be
recreated... it could just be a version thing.

Realize that, no matter what, if you are being identified as
root, then you will not be able to get access to ~root/.ssh's
contents if you give up your root-ness.

So that means you need to figure out how it's deciding you are
root.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



pam_unix.so error and lock order reversal

2002-04-13 Thread Rasmus Skaarup


Hello,

I have three issues.

1) When logging in, the following appears in messages:

Apr 13 12:18:37 laptop login: in openpam_dispatch(): pam_unix.so: no
pam_sm_open_session()
Apr 13 12:18:38 laptop login: in openpam_dispatch(): pam_unix.so: no
pam_sm_close_session()

2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
works fine. Is this somekind of security feature? :-)

3) lock order reversal when for instance doing a cvsup

Apr 13 12:16:58 laptop kernel: lock order reversal
Apr 13 12:16:58 laptop kernel: 1st 0xcc5928e4 KNOTE (UMA zone) @
/usr/src/sys/vm/uma_core.c:491
Apr 13 12:16:58 laptop kernel: 2nd 0xc082a724 PCPU KMAP ENTRY (UMA cpu) @
/usr/src/sys/vm/uma_core.c:1264

I'm running 5.0-CURRENT two hours old.


Thanks!


Best regards,
Rasmus Skaarup



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pam_unix.so error and lock order reversal

2002-04-13 Thread Terry Lambert

Rasmus Skaarup wrote:
 2) When logged in as root, and su'd to a non-root user, I cannot ssh to a
 4.5-STABLE machine.. It just hangs. But when logged in as non-root, it
 works fine. Is this somekind of security feature? :-)

Pretty much.  The user it attempts to log you in as is still
root, because that's still your identity, even if it's not
your current credential.  But your current credential does
not have access to the files for the remote system which are
necessary for your identity (~root/.ssh).

Ideally, identity would be handled by a session manager,
which was created at login time, which would maintain its
priviledges to these resources.


You might want to try using su - instead of su, in
order to actually *become* the other person.


-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message