devfs
[Top] [All Lists]

Re: devfs + xinit Authentication error

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: devfs + xinit Authentication error
From: Khimenko Victor <khim@xxxxxxxxxxxxxxxxx>
Date: Sun, 23 Apr 2000 00:31:34 +0400 (MSD)
Cc: Paul Jakma <paul@xxxxxxxx>, dgilbert@xxxxxxxxxxxx, linuxguy@xxxxxxxxxxxxxx, devfs@xxxxxxxxxxx
In-reply-to: <200004222007.e3MK76f15772@vindaloo.ras.ucalgary.ca>
Sender: owner-devfs@xxxxxxxxxxx

On Sat, 22 Apr 2000, Richard Gooch wrote:

> Paul Jakma writes:
> > On Thu, 2 Mar 2000, Khimenko Victor wrote:
> > 
> >   In <Pine.LNX.4.21.0003020000070.24029-100000@xxxxxxxxxxxxxxxx> Paul Jakma 
> > (paul@xxxxxxxx) wrote:
> >   > On Wed, 1 Mar 2000, Douglas Gilbert wrote:
> >   
> >   
> >   Exactly. And it's NOT what you want.
> >   
> >   > What's really needed is to fix the PAM securetty module. At the moment 
> > it
> >   > won't parse full paths like /dev/vc/6 - which imo means pam securetty is
> >   > broken.
> >   
> >   Oh, yeah. Of course PAM is broken. We need to embed telepathy in PAM
> >   IMMEDEATELY !
> > 
> > :)
> > 
> >  Or you can fix PAM so it will use full name after THAT
> >   -- cut --
> >       if ((tty = rindex(ttyn, '/')))
> >         ++tty;
> >       else
> >         tty = ttyn;
> >   -- cut --
> >   snippet from login.c ? PAM module was NEVER supplied with full device name
> >   to begin with. Add tiny patch to your login.c (from unix-utils) and stop
> >   blaming the innocent PAM.
> > 
> > sorry, i just presumed the brokenness was in PAM. thanks for pointing
> > the correct source of the problem. You should that submit that patch
> > to the utils-linux maintainer.
> 
> Can someone tell me what the status of this is? Has util-linux been
> fixed (it's not obvious from the 2.10k HISTORY)? If not, what's the
> patch that needs to be applied? And who will step forward and push it
> to Andries?
> 
It was applied in some 2.10<something> linux-utils ... Not remember which
but latest ones should work just fine... Since it's tiny change I think it
just not mentioned in HISTORY file...


<Prev in Thread] Current Thread [Next in Thread>