openssh unix dev - Jan 2002 - Strange read_passphrase behaviour ?

Hi,

I'm sorry if this has already come up on the list, I did a quick search
of the archive and didn't notice it.

I noticed IMHO strange behavior in read_passphrase:

If readpassphrase returns NULL and sets errno to ENOTTY, then
read_passphrase returns an empty passphrase to the caller instead of
error, now what happens with password authentication is that
if readpassphrase fails every time then ssh sends 3 empty passwords to
the server.

Is this the expected behaviour ?

-Jarno

-- 
Jarno Huuskonen <Jarno.Huuskonen at uku.fi>

why do you get ENOTTY?

should ssh auto-set Batchmode=yes for ENOTTY?

On Sun, Jan 27, 2002 at 10:56:24AM +0200, Jarno Huuskonen
wrote:
> Hi,
> 
> I'm sorry if this has already come up on the list, I did a quick search
> of the archive and didn't notice it.
> 
> I noticed IMHO strange behavior in read_passphrase:
> 
> If readpassphrase returns NULL and sets errno to ENOTTY, then
> read_passphrase returns an empty passphrase to the caller instead of
> error, now what happens with password authentication is that
> if readpassphrase fails every time then ssh sends 3 empty passwords to
> the server.
> 
> Is this the expected behaviour ?
> 
> -Jarno
> 
> -- 
> Jarno Huuskonen <Jarno.Huuskonen at uku.fi>
> _______________________________________________
> openssh-unix-dev at mindrot.org mailing list
> http://www.mindrot.org/mailman/listinfo/openssh-unix-dev