Re: ssh strangeness in -current...

[ just go back from one week of skiing, catching up ] According to Kris Kennaway: > 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. You'll hav

Re: ssh strangeness in -current...

Oliver Fromme <[EMAIL PROTECTED]> writes: > Apart from my stupidness of not checking the location of the > binary first -- what did I do wrong, and what's the recommended > way of handling this? Am I supposed to rm /usr/bin/ssh each > time I install a new release or snapshot? I can't believe >

Re: ssh strangeness in -current...

"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

Re: ssh strangeness in -current...

At 9:29 PM +0100 2000/3/7, Udo Erdelhoff wrote: > Are you using OpenSSH or the 'normal' ssh on your Solaris box? The Solaris box is the only place where I have tried installing OpenSSH so far. > @work: SunOS [...] 5.6 Generic_105181-05 [...] > SSH Version 1.2.27 [sparc-sun-solaris2.

Re: ssh strangeness in -current...

On 2000-Mar-08 13:55:45 +1100, Oliver Fromme <[EMAIL PROTECTED]> wrote: > I also had to remove >/etc/ssh. Somehow, /usr/local/bin/scp seems to pick up data >from /etc/ssh and tries to invoke /usr/bin/ssh, no matter >what. :-( I can't explain that. My installed-from-ports scp exec's /usr/local

Re: ssh strangeness in -current...

Peter Jeremy <[EMAIL PROTECTED]> wrote in list.freebsd-current: > I avoid the problem by structuring my paths along the lines of > $HOME/bin:/usr/local/bin:/usr/bin:/bin (everythere, not just on > FreeBSD). OK, I'll think I will do that (even though I didn't need it, until the /usr/bin/ssh pro

Re: ssh strangeness in -current...

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

Re: ssh strangeness in -current...

On Tue, 7 Mar 2000, Matthew N. Dodd wrote: > 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. >

Re: ssh strangeness in -current...

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

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Oliver Fromme wrote: > Apart from my stupidness of not checking the location of the binary > first -- what did I do wrong, and what's the recommended way of > handling this? Am I supposed to rm /usr/bin/ssh each time I install a > new release or snapshot? I can't believe that

Re: ssh strangeness in -current...

On Tue, 7 Mar 2000, Matthew N. Dodd wrote: > I've been building and rebuilding in an attempt to make sure that its not > some stupidity on my part. > > Be assured that when I'm positive I've got a reproducable error that I'll > let everyone in on the details. If you give us an idea wher

Re: ssh strangeness in -current...

Sheldon Hearn <[EMAIL PROTECTED]> wrote: > What about the off-by-one hostkey length problem? The client gives a warning when you connect to an old server with this problem. > Is it supposed to be possible to drop a "1024-bit" host key from > the old ssh1 port into /etc/ssh ? I have switched se

Re: ssh strangeness in -current...

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. Open

Re: ssh strangeness in -current...

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. Open

Re: ssh strangeness in -current...

Brad Knowles <[EMAIL PROTECTED]> wrote: > I've been following this thread for a while, and I'd like to ask > a related question -- can anyone else successfully use scp with > OpenSSH? An emphatic YES--for incrementally improving versions of OpenSSH over the last couple of months, on Free

Re: ssh strangeness in -current...

On Tue, Mar 07, 2000 at 06:48:56PM +0100, Brad Knowles wrote: > Must be a FreeBSD vs. Solaris thing Are you using OpenSSH or the 'normal' ssh on your Solaris box? I've just tried to copy files between my FreeBSD box @home and one of 'my' Solaris boxes @work. All four possible directions work exact

Re: ssh strangeness in -current...

On Tue, Mar 07, 2000 at 11:26:03AM +0200, Sheldon Hearn wrote: > Is it supposed to be possible to drop a "1024-bit" host key from the old > ssh1 port into /etc/ssh? It works for me. I've created my host key with ssh-1.2.26 and the base system OpenSSH accepted it without any problems. To Unsubsc

Re: ssh strangeness in -current...

In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes: : I know for a fact that one flag I used with ssh (ssh-agent's -p, I : think) does not exist in openssh. Nevertheless, I haven't had problems : with openssh. Well, actually, I haven't *tested* it, so who knows. :-) Other than the missing o

Re: ssh strangeness in -current...

On Tue, 7 Mar 2000, Jordan K. Hubbard wrote: > > I keep asking myself this question; a default sysinstall package would > > give us the same end result. > > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > breakage. > > Would you guys quit spreading FUD and star

Re: ssh strangeness in -current...

Kris Kennaway wrote: > > 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. I know for a fact that one flag I used with ssh (ssh-agent's -p, I th

Re: ssh strangeness in -current...

In article <[EMAIL PROTECTED]>, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > Ahh, so you can use the OpenSSH client to connect to some servers, but not > the F-Secure one? That would definitely be a bug you should report to the > OpenSSH developers. > > Is anyone else in the position to test th

Re: ssh strangeness in -current...

At 4:58 PM +0100 2000/3/7, Roland Jesse wrote: > Well, it works fine for me. Must be a FreeBSD vs. Solaris thing, because I've got the same version and it doesn't work for me. Sounds like I've got some more debugging to do. Thanks for all the info! -- These are my opini

Re: ssh strangeness in -current...

> I keep asking myself this question; a default sysinstall package would > give us the same end result. > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > breakage. Would you guys quit spreading FUD and start actually giving us some DETAILS on this alleged breakage?

Re: ssh strangeness in -current...

> 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 r

Re: ssh strangeness in -current...

> > Oliver Fromme writes: > > >As I said in my first message, it complained about a missing > > >RSA library. (To reproduce the actual error message word by > > >word, I'd have to install the whole stuff again.) > > > > you have to cvsup the secure stuff from internat. I did that and > >

Re: ssh strangeness in -current...

Brad Knowles <[EMAIL PROTECTED]> writes: > but I am wondering if scp with OpenSSH under FreeBSD does actually > work. Well, it works fine for me. r.arthur ~ % uname -rs FreeBSD 4.0-CURRENT r.arthur ~ % ssh -V SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. Roland

Re: ssh strangeness in -current...

lt;[EMAIL PROTECTED]> : Cc: FreeBSD-CURRENT <[EMAIL PROTECTED]> : Subject: Re: ssh strangeness in -current... : : At 10:17 AM -0500 2000/3/7, Matt Heckaman wrote: : : > When I tried out OpenSSH on a 3.4-stable machine, I as well was unable to : > scp into the machine from another 3.4-

Re: ssh strangeness in -current...

On Tue, Mar 07, 2000 at 03:55:52PM +0100, Brad Knowles wrote: > I've been following this thread for a while, and I'd like to ask > a related question -- can anyone else successfully use scp with > OpenSSH? On the one machine on which I've installed OpenSSH so far, > it appears that scp i

Re: ssh strangeness in -current...

At 10:17 AM -0500 2000/3/7, Matt Heckaman wrote: > When I tried out OpenSSH on a 3.4-stable machine, I as well was unable to > scp into the machine from another 3.4-stable machine using ssh 1.2.27, I > didn't at the time attempt to discover much, I was in a rush and thus just > installed 1.2.

Re: ssh strangeness in -current...

From: Brad Knowles <[EMAIL PROTECTED]> : To: [EMAIL PROTECTED] : Subject: Re: ssh strangeness in -current... : : At 1:10 AM +0100 2000/3/6, Oliver Fromme wrote: : : > I have upgraded a machine to the latest -current snapshot (it : > was running a -current from the end of Januar

Re: ssh strangeness in -current...

At 1:10 AM +0100 2000/3/6, Oliver Fromme 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. I've been

Re: ssh strangeness in -current...

On Mon, Mar 06, 2000 at 03:52:39PM -0700, Warner Losh wrote: > 2225: > OpenSSH has been added to FreeBSD. This may conflict with the > ports/security/ssh port since it installs binaries into > /usr/bin and the port goes into /usr/local/bin. Most paths > have /usr/bin

Re: ssh strangeness in -current...

Oliver Fromme <[EMAIL PROTECTED]> wrote: > I can't cvsup on that -current box, it's too small for a > "make world" (and probably too slow, too). I just downloaded > the 2228-current snapshot and installed it. In that case: See section 6.5 of the handbook. -- Christian "naddy" Weisgerber

Re: ssh strangeness in -current...

(Posted & mailed according to Reply-To) Gary Jennejohn <[EMAIL PROTECTED]> wrote in list.freebsd-current: > Oliver Fromme writes: > >As I said in my first message, it complained about a missing > >RSA library. (To reproduce the actual error message word by > >word, I'd have to install the wh

Re: ssh strangeness in -current...

Oliver Fromme writes: >Kris Kennaway <[EMAIL PROTECTED]> wrote in list.freebsd-current: > > Without still having seen the error message you were confused by, I can't > > do much else to help. I can't think of a better way to explain how to fix > > the problem than what's currently there. > >As I s

Re: ssh strangeness in -current...

Kris Kennaway <[EMAIL PROTECTED]> wrote in list.freebsd-current: > Without still having seen the error message you were confused by, I can't > do much else to help. I can't think of a better way to explain how to fix > the problem than what's currently there. As I said in my first message, it

Re: ssh strangeness in -current...

On Mon, 06 Mar 2000 13:32:00 MST, Warner Losh wrote: > : This sounds bad. Are you referring to the -o syntax differences, or > : actual incompatabilities? > > I'm talking about the -o syntax difference specifically. How does the > following sound? What about the off-by-one hostkey length prob

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Oliver Fromme wrote: > Apart from my stupidness of not checking the location of the binary > first -- what did I do wrong, and what's the recommended way of > handling this? Am I supposed to rm /usr/bin/ssh each time I install a > new release or snapshot? I can't believe that

Re: ssh strangeness in -current...

On Tue, 7 Mar 2000, Oliver Fromme wrote: > > Did you read the error message? > > Yes, I did, it was not helpful. In fact, it was confusing. Without still having seen the error message you were confused by, I can't do much else to help. I can't think of a better way to explain how to fix the p

Re: ssh strangeness in -current...

Kris Kennaway <[EMAIL PROTECTED]> wrote in list.freebsd-current: > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > the ports (yeah, stupid me), to no avail. It complained about some > > RSA library missing. > > Did you read the error message? Yes, I did, it was not helpful. In fact, it was c

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Warner Losh wrote: > Is this any better? I've removed the emotionally charged > compatibility word. Some more picking :) > 2225: > OpenSSH has been added to FreeBSD. This may conflict with the > ports/security/ssh port since it installs binaries into >

Re: ssh strangeness in -current...

Is this any better? I've removed the emotionally charged compatibility word. 2225: OpenSSH has been added to FreeBSD. This may conflict with the ports/security/ssh port since it installs binaries into /usr/bin and the port goes into /usr/local/bin. Most paths

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Arindum Mukerji wrote: > Also, going from an OpenSSH 1.2.2 box to an SSH-1.2.27 box is fine - it > coughs up a hairball when going to the F-Secure 1.3.7 commercial variant > though. Ahh, so you can use the OpenSSH client to connect to some servers, but not the F-Secure one? T

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, David Malone wrote: > I'd leave it saying that it isn't 100% compatible - it may sound > bad but it's true. There are several other things that aren't the > same: default options are different, some options have been removed > (AllowHosts is one that I know of), it produces wa

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Warner Losh wrote: > +2225: > + OpenSSH has been added to FreeBSD. This may conflict with the > + ssh port since it installs binaries into /usr/bin and the port You probably should refer to the ports by name: /usr/ports/security/ssh and /usr/ports/security/openss

Re: ssh strangeness in -current...

If memory serves me right, David Malone wrote: > On Mon, Mar 06, 2000 at 01:32:00PM -0700, Warner Losh wrote: > > > : > + 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

Re: ssh strangeness in -current...

On Mon, Mar 06, 2000 at 01:32:00PM -0700, Warner Losh wrote: > : > + 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 unsubsta

Re: ssh strangeness in -current...

In message <[EMAIL PROTECTED]> Kris Kennaway writes: : 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 Thanks. : > + Openssh isn't 100% compatible with ssh,

Re: ssh strangeness in -current...

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 b

Re: ssh strangeness in -current...

Warner Losh wrote: > + You will also need to enable openssh in /etc/rc.conf if you > + want to run the new servers. You may need to move your key > + and other config files from /usr/local/etc to /etc. Looks fine except config files go in /etc/ssh, not /etc. Jim Bloom [EMAIL P

Re: ssh strangeness in -current...

In message <[EMAIL PROTECTED]> Jim Bloom writes: : Did Warner include this with his changes to UPDATING about openssh in : the base system (which I haven't seen yet). No. I didn't, but I will. Here's my current draft that I'll commit after a while... Index: UPDATING ===

Re: Discussions and "facts" [Was: Re: ssh strangeness in -current...]

Marc Schneiders wrote: > > I find it quite a problem that one is supposed to read very long > threads of discussions (which one may not be interested in, does not > have the time for, or cannot understand) in order to find the > information necessary to run and keep up with current without > prob

Discussions and "facts" [Was: Re: ssh strangeness in -current...]

On Sun, 5 Mar 2000, Kris Kennaway wrote: > I'm quite surprised you've missed any discussion of OpenSSH here though, > since it's probably been one of the most discussed topics here for the > past few weeks. > I find it quite a problem that one is supposed to read very long threads of discussion

Re: ssh strangeness in -current...

John Baldwin wrote: > > On 06-Mar-00 Kris Kennaway wrote: > > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > > >> the ports (yeah, stupid me), to no avail. It complained about some > >> RSA library missing. > > > > Did you read the error message? Perhaps you should. Perhaps reporting it > > here w

Re: ssh strangeness in -current...

On 06-Mar-00 Warner Losh wrote: > In message Garance A Drosihn writes: >: My guess is that when he said "help someone to actually fix your problem", >: his desire was to fix it so people would NOT have a problem updating. > > I've added a blurb to UPDATING

Re: ssh strangeness in -current...

At 5:06 PM -0800 2000/3/5, Kris Kennaway wrote: > Enough people wanted it in the base system - in fact, when the question > was asked about importing it, I don't recall any objections - certainly it > was not a significant opposition. In fact, there are a lot of us that explicitly *di

Re: ssh strangeness in -current...

In message Garance A Drosihn writes: : My guess is that when he said "help someone to actually fix your problem", : his desire was to fix it so people would NOT have a problem updating. I've added a blurb to UPDATING. Warner To Unsubscribe: send mail to

Re: ssh strangeness in -current...

At 11:23 PM -0500 3/5/00, John Baldwin wrote: >On 06-Mar-00 Kris Kennaway wrote: > > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > > >> the ports (yeah, stupid me), to no avail. It complained about some > >> RSA library missing. > > > > Did you read the error message? Perhaps you should. Perhaps r

Re: ssh strangeness in -current...

"Matthew N. Dodd" wrote: > > On Sun, 5 Mar 2000, Kris Kennaway wrote: > > On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > > breakage. > > > > I can't fix this if you don't tell me what it is! > > What? Nobody else i

Re: ssh strangeness in -current...

On 06-Mar-00 Kris Kennaway wrote: > On Mon, 6 Mar 2000, Oliver Fromme wrote: > >> the ports (yeah, stupid me), to no avail. It complained about some >> RSA library missing. > > Did you read the error message? Perhaps you should. Perhaps reporting it > here would help someone to actually fix yo

Re: ssh strangeness in -current...

On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > > breakage. > > > > I can't fix this if you don't tell me what it is! > > What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? Your message wasn't clear y

Re: ssh strangeness in -current...

On Sun, 5 Mar 2000, Kris Kennaway wrote: > On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > breakage. > > I can't fix this if you don't tell me what it is! What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH

Re: ssh strangeness in -current...

On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > breakage. I can't fix this if you don't tell me what it is! Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTEC

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Oliver Fromme wrote: > the ports (yeah, stupid me), to no avail. It complained about some > RSA library missing. Did you read the error message? Perhaps you should. Perhaps reporting it here would help someone to actually fix your problem instead of having to guess. > PS:

Re: ssh strangeness in -current...

On Mon, 6 Mar 2000, Oliver Fromme wrote: > By the way, _why_ is ssh in the base system now, and what is wrong > with having it in the ports? I'm sorry if there was a "HEADS UP" on > this list, then I must have missed it. I keep asking myself this question; a default sysinstall package would give

ssh strangeness in -current...

Hi, 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. At first I was very suprised and had no clue what was going on. I couldn'