devfs
[Top] [All Lists]

Re: /etc/securetty problem

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: /etc/securetty problem
From: Frédéric L. W. Meunier <0@xxxxxxxxxxxxxx>
Date: Wed, 7 Mar 2001 00:08:18 -0300
Cc: devfs@xxxxxxxxxxx
In-reply-to: <200102171835.f1HIZ9n12590@mobilix.atnf.CSIRO.AU>; from rgooch@ras.ucalgary.ca on Sun, Feb 18, 2001 at 05:35:09AM +1100
References: <20010202000527.I160@pervalidus.dyndns.org> <200102142115.f1ELFVV00392@mobilix.ras.ucalgary.ca> <20010216030017.X1922@pervalidus.dyndns.org> <200102171835.f1HIZ9n12590@mobilix.atnf.CSIRO.AU>
Sender: owner-devfs@xxxxxxxxxxx
User-agent: Mutt/1.3.16i
Strange. After a reboot I was able to log in without any
changes to shadow, and using vc/* in both /etc/inittab and
/etc/securetty. I can log in as root and as a normal user.

For some reason it didn't work in my only boot with 2.4.1, but
I don't know why. Maybe because I mounted devfs after booting
(I forgot to edit my sysinit script) and started devfsd just
after ? I don't know if it's a problem to mount devfs after you
log in, but it worked. What didn't work was pppd logging. init
1 -> init 3 wouldn't change the login problem, but fixed pppd.

Hopefully shadow seems to be devfs aware.

On Sun, Feb 18, 2001 at 05:35:09AM +1100, Richard Gooch wrote:
> 0@xxxxxxxxxxxxxx writes:
> > Hi Richard.
> > 
> > On Thu, Feb 15, 2001 at 08:15:31AM +1100, Richard Gooch wrote:
> > > 0@xxxxxxxxxxxxxx writes:
> > > > Hi. For the first time I installed devfs (Kernel 2.4.1). It's
> > > > working without any major problems, but I can't log as root on
> > > > any console if I change /etc/securetty to use vc/1 (I also
> > > > tried with 1) instead of tty1.
> > > 
> > > Check the FAQ. It talks about enabling root logins at the console.
> > 
> > I checked both Documentation/filesystems/devfs/README and
> > http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html
> > 
> > Are you talking about
> > http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html#quick-start,
> > the 'System Libraries ... /etc/securetty' part?
> 
> Yes.
> 
> > I use glibc 2.2.2 but don't have Linux-PAM installed
> > (Slackware uses shadow). I can use agetty from util-linux
> > without any problems (I set /etc/inittab to use vc/1 -> vc/4).
> > The problem is login. I can't use the one from util-linux
> > because it needs PAM. I have to use all authentication
> > programs from shadow.
> 
> OK. So it looks like shadow is broken.
> 
> > If I set /etc/securetty to use 1 or vc/1 root can't log in.
> > It works if I use tty1.
> 
> So perhaps the shadow code is hard-wired to use tty#, or perhaps it's
> broken the same way other code was and assumes that the devices are in
> /dev and not a subdirectory of /dev.
> 
> > The problem seems to be with login from shadow. I'd appreciate
> > any reports from Slackware users. Unfortunately, I think 99%
> > are using a distribution with PAM.
> > 
> > My system:
> > 
> > Linux Kernel 2.4.1 on x86
> > shadow-20000902: login
> > util-linux-2.10s: agetty
> 
> Can you please check through the shadow code to find out what's going
> wrong, and then send a patch to the shadow maintainer? Let me know if
> there are any workarounds (or fixed versions of shadow that can be
> installed), so I can update the FAQ.

-- 
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)

<Prev in Thread] Current Thread [Next in Thread>
  • Re: /etc/securetty problem, Frédéric L. W. Meunier <=