On Mon, 6 Mar 2000, Warner Losh wrote: > + want to run the new servers. You may need to move your key > + and other config files from /usr/local/etc to /etc. /etc/ssh > + Openssh isn't 100% compatible with ssh, so some care needs to > + be taken in its operation. This sounds bad. Are you referring to the -o syntax differences, or actual incompatabilities? There have been unsubstantiated reports of interoperability problems, but nothing well documented here. 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... Doug Barton
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... John Baldwin
- Re: ssh strangeness in -current... Garance A Drosihn
- Re: ssh strangeness in -current... Warner Losh
- Re: ssh strangeness in -current... John Baldwin
- Re: ssh strangeness in -current... Jim Bloom
- Re: ssh strangeness in -current... Warner Losh
- Re: ssh strangeness in -current... Jim Bloom
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Warner Losh
- Re: ssh strangeness in -current... David Malone
- Re: ssh strangeness in -cur... Bruce A. Mah
- Re: ssh strangeness in -cur... Kris Kennaway
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Sheldon Hearn
- Re: ssh strangeness in -cur... Udo Erdelhoff
- Re: ssh strangeness in -cur... Christian Weisgerber
- Re: ssh strangeness in -current... Warner Losh
- Re: ssh strangeness in -current... Kris Kennaway