"Jordan K. Hubbard" wrote: > > > I have upgraded a machine to the latest -current snapshot (it > > was running a -current from the end of January before). Every- > > thing went fine, except for one thing: ssh didn't work anymore. > > It used to work fine before. > > You really need to read the -current mailing list if you're going to > run -current. Saying that openssh took you by surprise as a -current > user is sort of like saying you didn't know Elvis was dead. :-( but he isn't! He was working in a chip shop last I heard. Paul. 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... Brad Knowles
- 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