9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] infauth factotum bug?
Date: Wed,  7 May 2008 21:16:12 -0400	[thread overview]
Message-ID: <20080508011612.GY4503@peregrine.cs.jhu.edu> (raw)
In-Reply-To: <df49a7370805070300w7e481dddi2d20d78b61db9f44@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Wed, May 07, 2008 at 11:00:13AM +0100, roger peppe wrote:
> On Tue, May 6, 2008 at 9:38 PM, Nathaniel W Filardo <nwf@cs.jhu.edu> wrote:
> >  term% cpu -h sea.cs.jhu.edu -k 'user=nwf'
> 
> i think the answer may be to do with the fact
> that you're using "-k 'user=foo'" rather than "-u foo".
> i haven't got time to look into it
> properly right now, but it's worth trying.
> 
>   rog.

No change: nwf@ then bootes@ asks for two passwords, but still can log in as
nwf@ without a password after logging in as bootes@ and can't log in as me@
without one.  Indeed, this is expected as a cursory inspection of
/sys/src/cmd/cpu.c suggests that the only authentication changes made by -u
are as if the user had typed -k 'user=...' intead (there are some small
changes made in the file system code it seems to make uid and gid match the
argument of -u which doesn't happen with -k, but these ought not impact
authentication).

Thanks much.
--nwf;

[-- Attachment #2: Type: application/pgp-signature, Size: 192 bytes --]

  reply	other threads:[~2008-05-08  1:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080505154136.GP4503@peregrine.cs.jhu.edu>
     [not found] ` <5932ecefbd9063a70069a114a0a37b26@vitanuova.com>
2008-05-06 20:38   ` Nathaniel W Filardo
2008-05-07 10:00     ` roger peppe
2008-05-08  1:16       ` Nathaniel W Filardo [this message]
2008-05-08 14:02     ` Russ Cox
2008-05-09  1:31       ` Nathaniel W Filardo
2008-05-09  1:48         ` erik quanstrom
2008-05-09 13:07         ` Russ Cox

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=20080508011612.GY4503@peregrine.cs.jhu.edu \
    --to=nwf@cs.jhu.edu \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).