Problem with OpenSSH with UseLogin.. AGAIN!!!

Markus Friedl Markus.Friedl at informatik.uni-erlangen.de
Fri Jun 1 23:37:35 EST 2001


On Fri, Jun 01, 2001 at 04:08:16PM +0300, Pekka Savola wrote:
> On Fri, 1 Jun 2001, Markus Friedl wrote:
> 
> > On Fri, Jun 01, 2001 at 02:47:21PM +0200, Krzysztof Oledzki wrote:
> > >
> > >
> > > On Sat, 26 May 2001, Markus Friedl wrote:
> > >
> > > > On Sat, May 26, 2001 at 12:15:42PM +1000, Andrew Bartlett wrote:
> > > > > Its not a bug, its a feature :-)  Seriously, if UseLogin is selected
> > > > > then the sys-admin has dictated that all authentictions must pass though
> > > > > /bin/login - usually for local secuirty reasons.  Disabling this kind of
> > > > > defeats the purpose of the option.
> > > >
> > > > no, this is not true.
> > > >
> > > > use_login is ignored if you specify commands.
> > > >
> > > So? Someone will fix it!? It is quite stiupid to keep this bug!!!
> >
> > no, it's not a bug, it's a feature.
> 
> I think some people rely on UseLogin to perform additional login logging,
> checking etc.  For them, this might appear as a huuuge problem.

i don't think that ssh ever did this. login is just used to
update wtmp, print "you have new mail"

however, you cannot say
	/usr/bin/login user -c command
so you cannot use login(1) for command execution.
but for command execution, you don't need
to touch wtmp or print "you have new mail".

even the manpage says:

     UseLogin
             Specifies whether login(1) is used for interactive login ses-
             sions.  Note that login(1) is never used for remote command exe-
             cution.  The default is ``no''.

but it would be better if i never did accept the patch
that added use_login.......



More information about the openssh-unix-dev mailing list