This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: BUG: ssh.exe ProtocolKeepAlives option broken
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 21 Jul 2004 10:22:08 +0200
- Subject: Re: BUG: ssh.exe ProtocolKeepAlives option broken
- References: <410730CA.9020701@hot.ee>
- Reply-to: cygwin at cygwin dot com
On Jul 28 07:51, Float wrote:
> |>Summary: Cygwin ssh.exe doesn't accept the 'ProtocolKeepAlives' option
> |>
> |>Example:
> |>C:\sshclient>ssh -o ProtocolKeepAlives=180 example.com
> |>command-line: line 0: Bad configuration option: ProtocolKeepAlives
> |
> |AFAICT, ProtocolKeepAlives is not mentioned in the manpage for ssh.
> |So, this isn't a bug.
>
> Indeed, it seems that it is not mentioned in the Cygwin ssh_config manpage.
>
> However, that option should be supported according to the following
> Corinna Vinschen mail:
> http://sources.redhat.com/ml/cygwin/2002-01/msg00323.html
>
> Btw, the ProtocolKeepAlives is a must for using ssh for port forwarding
> behind a firewall that drops inactive connections.
ProtocolKeepAlives has been dropped a couple of OpenSSH versions before.
See `man sshd_config' for ClientAliveInterval and ClientAliveCountMax,
`man ssh_config' for ServerAliveInterval and ServerAliveCountMax, or
both for TCPKeepAlive.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Co-Project Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/