On 1/16/07, Darren Tucker <[EMAIL PROTECTED]> wrote:
OpenSSH's client traditionally set TCP_NODELAY for "interactive" sessions
(where "interactive" means "has requested a pty", although that's
becoming less and less useful as an indicator). You can
nce. We have fixed this on a plain socket connection by
> setting TCP_NODELAY.
>
> I have looked at the man pages and the e-mail archives and as far as I
> can tell there is no way to set this for an ssh subsystem. Am I
> correct?
OpenSSH's client traditionally set TCP_NODELAY f
cure. I have configured the system to use an openssh subsystem
> and it works well except that we have noticed some inconsistent
> performance. We have fixed this on a plain socket connection by
> setting TCP_NODELAY.
>
> I have looked at the man pages and the e-mail archives and as
Hello,
I have an interactive application including mouse events that I want
to be secure. I have configured the system to use an openssh subsystem
and it works well except that we have noticed some inconsistent
performance. We have fixed this on a plain socket connection by
setting TCP_NODELAY
in socket connection by
> setting TCP_NODELAY.
>
> I have looked at the man pages and the e-mail archives and as far as I
> can tell there is no way to set this for an ssh subsystem. Am I
> correct?
>
> Thank you,
> Chris
>
Hello,
I have an interactive application including mouse events that I want
to be secure. I have configured the system to use an openssh subsystem
and it works well except that we have noticed some inconsistent
performance. We have fixed this on a plain socket connection by
setting TCP_NODELAY
