Heather, Daniel, Drew and list.
Drew pointed out that ssh2 is the commercial version and only handles SSH2
on it's own. I installed ssh (unstable package ) which is the OpenSSH
version and chose to replace my old config files with the ones in the
package, and it handles both SSH2 and degrade
Heather, Daniel, Drew and list.
Drew pointed out that ssh2 is the commercial version and only handles SSH2
on it's own. I installed ssh (unstable package ) which is the OpenSSH
version and chose to replace my old config files with the ones in the
package, and it handles both SSH2 and degrad
On Fri, Feb 23, 2001 at 05:52:28PM -0500, [EMAIL PROTECTED] wrote:
>
> Heather and the list.
>
> > *Now* I'll try to answer the right question :D
> >
> >a) unstable's 'ssh' is OpenSSH, deb version 1:2.3.0p1-1.13
> > testing's 'ssh' is OpenSSH, deb version 1:1.2.3-9.2
> >
Sorry about over messaging the list.
> I found that even though it wasn't a commented out option in the ssh2
> config file the man page claims that 'Ssh1compatibility yes' is a
> configuration option. I added it to ssh2.conf and I still get an illegal
> protocol error from the SSH1 server.
> I'm still searching for the way to config this to degrade to SSH1
> automatically.
Adding more to my own message.
I found that even though it wasn't a commented out option in the ssh2
config file the man page claims that 'Ssh1compatibility yes' is a
configuration option. I added it to ssh2.co
> If nothing else, try using the '-1' and '-v' arguments to ssh. '-1' asks
> for protocol one only, '-v' shows debug messages about the progress.
I'd been using -v, that's how I know when I use the wrong protocol.
-1 is an illegal option. :( Too bad, that would have been fine.
So. I thou
On Fri, Feb 23, 2001 at 05:52:28PM -0500, [EMAIL PROTECTED] wrote:
>
> Heather and the list.
>
> > *Now* I'll try to answer the right question :D
> >
> >a) unstable's 'ssh' is OpenSSH, deb version 1:2.3.0p1-1.13
> > testing's 'ssh' is OpenSSH, deb version 1:1.2.3-9.2
> >
Sorry about over messaging the list.
> I found that even though it wasn't a commented out option in the ssh2
> config file the man page claims that 'Ssh1compatibility yes' is a
> configuration option. I added it to ssh2.conf and I still get an illegal
> protocol error from the SSH1 server.
> I'm still searching for the way to config this to degrade to SSH1
> automatically.
Adding more to my own message.
I found that even though it wasn't a commented out option in the ssh2
config file the man page claims that 'Ssh1compatibility yes' is a
configuration option. I added it to ssh2.c
> If nothing else, try using the '-1' and '-v' arguments to ssh. '-1' asks
> for protocol one only, '-v' shows debug messages about the progress.
I'd been using -v, that's how I know when I use the wrong protocol.
-1 is an illegal option. :( Too bad, that would have been fine.
So. I tho
On Fri, 23 Feb 2001, [EMAIL PROTECTED] wrote:
[...]
> I can't connect to ssh1 now, but I'm sure I can config it to drop back
> automatically, besides what I really needed was Protocol 2, I had to
> connect to a machine which has no telnetd and only listens sshd Prot
> 2.
If nothing else, try usi
Heather and the list.
> *Now* I'll try to answer the right question :D
>
>a) unstable's 'ssh' is OpenSSH, deb version 1:2.3.0p1-1.13
> testing's 'ssh' is OpenSSH, deb version 1:1.2.3-9.2
> not good enough to stick with testing :(
Actually I didn't install the unstabl
Forwarded back into the list because it's important :) It isn't really
laptop-ish anymore, but we laptop folks use ssh *a lot*!
I went back and looked at the descriptions - he's right, it does say OpenSSH,
but it does *not* says SSH2 support...
...and the version isn't OpenSSH 2.3.0, it's 1.2 so
On Fri, 23 Feb 2001, [EMAIL PROTECTED] wrote:
[...]
> I can't connect to ssh1 now, but I'm sure I can config it to drop back
> automatically, besides what I really needed was Protocol 2, I had to
> connect to a machine which has no telnetd and only listens sshd Prot
> 2.
If nothing else, try us
Heather and the list.
> *Now* I'll try to answer the right question :D
>
>a) unstable's 'ssh' is OpenSSH, deb version 1:2.3.0p1-1.13
> testing's 'ssh' is OpenSSH, deb version 1:1.2.3-9.2
> not good enough to stick with testing :(
Actually I didn't install the unstab
Forwarded back into the list because it's important :) It isn't really
laptop-ish anymore, but we laptop folks use ssh *a lot*!
I went back and looked at the descriptions - he's right, it does say OpenSSH,
but it does *not* says SSH2 support...
...and the version isn't OpenSSH 2.3.0, it's 1.2 s
Heather and Daniel and all the list.
I added unstable to my sources.list (testing didn't have it) and got ssh2
via apt-get and I can now connect via ssh Protocol 2. I then removed the
unstable lines from my sources.list and updated, it seems I'm back to just
cacheing the stable stuff, but no
Heather and Daniel and all the list.
I added unstable to my sources.list (testing didn't have it) and got ssh2
via apt-get and I can now connect via ssh Protocol 2. I then removed the
unstable lines from my sources.list and updated, it seems I'm back to just
cacheing the stable stuff, but n
Heather, Daniel, et al..
I'm going to take a look at my situation here tonight at finding and
loading ssh2 and make a full report to the list.
I'm just giving a status report. Thanks for the tips.
brew
Heather, Daniel, et al..
I'm going to take a look at my situation here tonight at finding and
loading ssh2 and make a full report to the list.
I'm just giving a status report. Thanks for the tips.
brew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
> On Wed, 21 Feb 2001, [EMAIL PROTECTED] wrote:
> > Is it safe to run the non-stable software package ssh2?
>
> Within the bounds of common sense, yes. I do.
>
> > Can I safely use apt-get to install it on my Dell laptop?
> Yes. Be aware that it will probably bring in a new libc and a few other
> On Wed, 21 Feb 2001, [EMAIL PROTECTED] wrote:
> > Is it safe to run the non-stable software package ssh2?
>
> Within the bounds of common sense, yes. I do.
>
> > Can I safely use apt-get to install it on my Dell laptop?
> Yes. Be aware that it will probably bring in a new libc and a few othe
>
> Is it safe to run the non-stable software package ssh2? Can I safely use
> apt-get to install it on my Dell laptop? I guess my question is really -
> does non-stable mean it is unsafe, or just not garanteed to be safe.
> Will an apt-get installation still check for conflicts and dependenc
>
> Is it safe to run the non-stable software package ssh2? Can I safely use
> apt-get to install it on my Dell laptop? I guess my question is really -
> does non-stable mean it is unsafe, or just not garanteed to be safe.
> Will an apt-get installation still check for conflicts and dependenci
On Wed, 21 Feb 2001, [EMAIL PROTECTED] wrote:
> Is it safe to run the non-stable software package ssh2?
Within the bounds of common sense, yes. I do.
> Can I safely use apt-get to install it on my Dell laptop?
Yes. Be aware that it will probably bring in a new libc and a few other
bits...
> I
On Wed, 21 Feb 2001, [EMAIL PROTECTED] wrote:
> Is it safe to run the non-stable software package ssh2?
Within the bounds of common sense, yes. I do.
> Can I safely use apt-get to install it on my Dell laptop?
Yes. Be aware that it will probably bring in a new libc and a few other
bits...
>
Is it safe to run the non-stable software package ssh2? Can I safely use
apt-get to install it on my Dell laptop? I guess my question is really -
does non-stable mean it is unsafe, or just not garanteed to be safe.
Will an apt-get installation still check for conflicts and dependencies?
And w
Is it safe to run the non-stable software package ssh2? Can I safely use
apt-get to install it on my Dell laptop? I guess my question is really -
does non-stable mean it is unsafe, or just not garanteed to be safe.
Will an apt-get installation still check for conflicts and dependencies?
And
28 matches
Mail list logo
