On Tue, 7 Mar 2000, John Polstra wrote:
> In the past I have had interoperability problems between F-Secure
> and the open source versions of ssh. But the cause then was simply
> that the F-Secure keys were too long (> 1024 bits) for ssh's rsaref
> to cope with.
That would certainly do it. OpenSSH should probably print a more helpful
error message in this case, though.
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... 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
- Re: ssh strangeness in -current... John Hay
- Re: ssh strangeness in -current... Kris Kennaway
