OpenStep (NeXT) and TTY modes

[Nicolas Williams]

On Wed, Oct 31, 2001 at 12:40:03PM -0800, Kevin Steves wrote:
> On Wed, 31 Oct 2001, Nicolas Williams wrote:
> :OpenStep, apparently, does not initialize new pty/tty modes to a sane
> :default.
> :
> :I'm thinking this code snippet, added to tty_parse_modes() before the
> :for(;;) loop should suffice:
> :
> :#ifdef HAVE_NEXT
> :	tio.c_oflag |= ONLCR;
> :	tio.c_lflag |= ECHO;
> :#endif /* HAVE_NEXT */
> :
> :Also, I've noticed that "ssh -t next_host stty" gives different output
> :than an interactive session to the same NeXT... I suspect that this
> :means that the SSH client is sending a different set of tty modes to the
> :sshd on the NeXT... Is that so? Does that make sense?
> 
> i don't know.  is in the same for protocol 1 and 2?  you can debug with
> ssh/-vvv sshd/-ddd for tty_make_modes() and tty_parse_modes().

I just did ssh -vvv -- I saw no difference in what the client sends...
Go figure...

I can't see why the sshd would not apply both the same way.  But mind
you, the client is OpenSSH 2.9p2 on Solaris, and the server is OpenSSH
2.9p2 on OpenStep.

No big deal. The patch to add tio.c_iflag |= INLCR, tio.c_oflag |=
ONLCR and tio.c_lflag |= ECHO suffices for me. We've tested with
OpenSSH clients and PUTTY.

Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.