On Tue, 7 Mar 2000, Doug Barton wrote: > If you give us an idea where your breakage is, we can tell you if > it's a known problem. E.g., there is a known problem with PPP(D) and > NO_OPENSSL that Kris and I have already worked out a fix for. I'm still waiting for Jordan's approval on that patch :-) <nudge, nudge> 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... Matthew N. Dodd
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Matthew N. Dodd
- Re: ssh strangeness in -current... Kris Kennaway
- Re: ssh strangeness in -current... Doug Barton
- Re: ssh strangeness in -current... Jordan K. Hubbard
- Re: ssh strangeness in -current... Matthew N. Dodd
- Re: ssh strangeness in -current... Doug Barton
- Re: ssh strangeness in -current... Matthew N. Dodd
- 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