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. Yep, thats one of them. We'll see if I find anything else. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- ssh strangeness in -current... Oliver Fromme
- 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 -curren... 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