On Mon, 6 Mar 2000, Arindum Mukerji wrote: > Also, going from an OpenSSH 1.2.2 box to an SSH-1.2.27 box is fine - it > coughs up a hairball when going to the F-Secure 1.3.7 commercial variant > though. Ahh, so you can use the OpenSSH client to connect to some servers, but not the F-Secure one? That would definitely be a bug you should report to the OpenSSH developers. Is anyone else in the position to test this? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: ssh strangeness in -current... Matt Heckaman
- Re: ssh strangeness in -current... Harold Gutch
- Re: ssh strangeness in -current... Roland Jesse
- Re: ssh strangeness in -current... Brad Knowles
- Re: ssh strangeness in -current... Udo Erdelhoff
- Re: ssh strangeness in -current... Brad Knowles
- Re: ssh strangeness in -current... Christian Weisgerber
- Re: ssh strangeness in -current... Jordan K. Hubbard
- Re: ssh strangeness in -current... Paul Richards
- Re: ssh strangeness in -current... Kai Großjohann
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... John Polstra
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Oliver Fromme
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Peter Jeremy
- Re: ssh strangeness in -current... Christian Weisgerber
- Re: ssh strangeness in -current... Peter Jeremy
- Re: ssh strangeness in -current... Oliver Fromme
- Re: ssh strangeness in -current... Gary Jennejohn
- Re: ssh strangeness in -current... Oliver Fromme