sshd1 v1.2.26, b20.1, tty problems (most likely)

Juha Jäykkä
Mon May 10 22:44:00 GMT 1999

> >bash$ ps
> >   1024   0  11:24:29 /H-i586-cygwin32/bin/bash.exe
> >   1316  -1  13:32:54 /usr/local/sbin/sshd1.exe
> >   1317   1  13:32:57 /bin/ps.exe
> >   1087   1  11:37:20 /H-i586-cygwin32/bin/bash.exe
> >bash$ ssh1 bash --login -i
> Set "CYGWIN=tty" in the global environment settings
> (CP/System/Environment) and reboot. Don't forget to copy your mount
> settings (if differs from default) into cygwin's global mount table

  No help. Nothing changes. sshd1 still receives TTY -1, ls complains
about bad file number and something causes a logout from my newly
created shell immediately. I ran ssh1 -v <ip> bash --login -i. Here's
the result. Hope this helps figure this out (stiff is my computer's
netbios name):
bash$ ssh1 -v bash --login -i
SSH Version 1.2.26 [i586-pc-cygwin32], protocol version 1.5.
Standard version.  Does not use RSAREF.
stiff: ssh_connect: getuid 1045 geteuid 1045 anon 1
stiff: Connecting to port 22.
stiff: Connection established.
stiff: Remote protocol version 1.5, remote software version 1.2.26
stiff: Waiting for server public key.
stiff: Received server public key (768 bits) and host key (4096 bits).
stiff: Host '' is known and matches the host key.
stiff: Initializing random; seed file /.ssh/random_seed
stiff: Encryption type: idea
stiff: Sent encrypted session key.
stiff: Installing crc compensation attack detector.
stiff: Received encrypted confirmation.
stiff: No agent.
stiff: Doing password authentication.
juhaj@'s password:
stiff: Sending command: bash --login -i
stiff: Entering interactive session.
bash: no job control in this shell
ls: write error: Bad file number
bash: /home/juhaj/.bashrc: Permission denied
bash-2.02$ logout
stiff: Transferred: stdin 0, stdout 131, stderr 0 bytes in 0.7 seconds
stiff: Bytes per second: stdin 0.0, stdout 187.1, stderr 0.0
stiff: Exit status 126

  As you can see, nothing gets sent from connecting side but destination
side receives an EOF from somewhere. Looks like this supports my
assumption that the problem is with the odd TTY number. 
  So, what comes next?

Juha Jäykkä,
PS See for latest version of RSA in
Here goes the RSA code in two lines:
print pack"C*",split/\D+/,`echo

Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list