Many thanks to everyone who has responded!
> -----Original Message-----
> I am running digital unix 4.0d and cannot upgrade to 5.0 yet due to
application restrictions.
> I need to start using ssh but would prefer ssh2 ... The ssh website does
not list Tru64 4.x
> on alpha as a supported system but I am wondering if anyone has run it on
a 4.0d system?
> If so, can you share your experiences?
----- addendum -----
It turns out that the system(s) running SSH2 will be 4.0f, not 4.0d. In
either case,
it seems as though it will run fine with minor caveats (see individual
responses below):
> Built great. No problems. Except ssh1 clients cannot connect unless you
also have ssh1 installed and ssh2 pointing to it.
> - Mark
> We haven't had any problems with ssh2 version 2.0.13 on v.0d systems, or
4.0F systems.
> Build is pretty straightforward with no problems.
- Ben
> I am running ssh2.0.13 on 4.0E with out problems. For compatibility with
other sites you need to also install ssh1.2.27
> Installation was straightforward ssh1 first then ssh2 and then configure
for ssh1 compatibility, all well documented in
> the readme's.
- Eric
> It runs perfectly. We have 2.0.12, and I believe it compiled out of the
box.
- Serguei
> For what it's worth, I've compiled and run both versions under 4.0D.
> They also seem to work on 5.0.
> In fact, you can just move binaries, though the source compiles also.
- Frank
> We are running ssh2 with ssh1 compatibility mode on 4.0E with no problems.
4.0E differs from 4.0D mainly in the
> Enhanced Security database structure. Some systems have Enhanced security
turned on and some do not. Most client
> systems are running Linux, also ssh2 with ssh1 compatibility mode: we have
some clients that need to run ssh1, and
> many external systems still run ssh1 only, hence the compatibility mode.
ssh2 is better.
ssh-1.2.27
ssh-2.0.13
> Compiled with DEC C compiler: our install of gcc bombed. If you have gcc,
> run
> setenv CC cc
> (csh)
> or
> CC=cc ; export CC
> (sh or ksh)
> before running configure to force use of cc if gcc doesn't work, otherwise
> gcc is preferred.
>
-Larye
> we are running ssh2 on 4.0d. the only problems we see are:
> 1) you need to compile in to default back to ssh1 when it encounters
an older version
> 2) you need to leave on scp1 because scp2 will not default back to
scp1 - at least that I could find.
> otherwise, it works great.
- Claudia
> I run SSH V1.2.27 on V4.0B and V4.0F (no NIS, though). No problems to
date.
> Please note that the license conditions for SSH 2.0.x are much more
restrictive.
- Rolf-Peter
> We've used it somewhat, and it seems to work ok. ssh2 v2.0.13 does not
> have some of the features we use, such as tcp wrappers. I have not looked
at v2.1.0 yet.
- Mike
> I am running ssh version 2 on a v4.0D system. It works fine except for a
> problem with the root account I previously posted to this group.
- Larry
> I have been running ssh2 for quite sometime on Tru64 4.0d and 4.0f.
- Zhi-Wei Lu
> we use ssh and also ssh2 on our machines which run 4.0d or 4.0f. No
> problems at all. You have to compile the software for
> yourself via configure and make. I did this quite some time ago and
> therefore cannot remember if there were any problems
> but I don't think so. Be careful with the config files, especially
> regarding the ssh1 compatibility settings of an ssh2 server.
> Don't forget to write your own startup and shutdown scripts in rc0.d,
> rc2.d and rc3.d. Pay attention to the license of ssh1 and ssh2.
- Ralf
> This is no problem, you just have to compile the source.
> Also be sure to use at least version 2.13.1. Older versions have problems
> with X.11 display.
- Felix
> We are running ssh 1.2.26, 1.2.27, 1.3.7, 2.0.13 and 2.0.13.2 on 4.0D. We
purchased the 1.3.7 and 2.0.13.2. The other
> versions were downloaded from the web. We had problems with the
compilation of 2.0.13.2 which have since been worked
> out and the 2.0.13.2 and 1.3.7 versions are working fine. When you upgrade
to a 2 version you must still have a 1 version
> on the system or the 1 clients can not connect. This was all done
seamlessly in the install of the 2 version. The 2.0.13
> version off the web compiled and installed fine, but the 2.0.13.2 version
needed 2 minor code changes to compile. There
> is a website that the FSecure people sent me that verifies the 4.0D works
with ssh2; however, I found the link unhelpful
> when it came to the 2 code changes we made.
> http://www.f-secure.com/support/ssh/unix/ssh2-sup-pf.html
>
> So far I have tested the connectivity between the above mentioned versions
including ssh, slogin, scp (between all 1 and 2
> versions), and sftp (between two machines running 2.0.13.2), and have had
no other problems other than the compile fixes.
- Debra
> I've been running 'sshd2' on a 4.0f with no problems.
> (So unless there's been a lot of changes between 4.0d and 4.0f, you should
be fine as well :)
- Brian
> I installed ssh-1.2.27 and then ssh-2.0.13 on a Tru64 V4.0E system. (We
needed ssh because we have a visitor whose
> home site doesn't work with ssh2 and this gives us both.) They both
installed "out-of-the-box" with no problems.
- Peter
> If you need enhanced security support, you'll have to use ssh2 2.0.13.
> They took out the enhanced security support in 2.1.
> OpenSSH is working in SSH2 support, and I've got some patches for it to
> make it use enhanced security. I haven't
> submitted them yet, but will soonish.
- John
> I have both compiled and running on a DS20 running Tru64 4.0F with no
> problems. IIRC I got the > sources from src.doc.ic.ac.uk (SUNsite).
> I can't see there being a problem necessarily with 4.0D.
- Joe
> I successfully compiled ssh2 from source on 4.0E using gcc 2.95.2. I did
> need to upgrade to that version of gcc (I think I had 2.8.1 before).
- Bryan
Joan Riggs
Raytheon RSE / KLS
Information Technology
805.355.9877
joan.riggs_at_kls.usaka.smdc.army.mil
Received on Thu Apr 13 2000 - 00:11:38 NZST