On Thu, 29 Jun 2000, Michael Osier wrote:
->I've been having a nightmare of a time trying to install SSH 2.2 on a
->DEC Alpha running OSF 4.0D. Has anyone had any luck with it?
->
->Originally, I had some problems at compile time. A couple of
->individuals at SSH's tech support were kind enough to give me some
->suggestions even though I'm an academic (non-commercial) user.
->Basically there were problems with the native compiler. I just
->installed GCC ver 2.95.2. Now the old errors are gone and I'm getting
->new errors:
->
->=======================================
->No suffix list.
->make all-recursive
->No suffix list.
->Making all in lib
->No suffix list.
->Making all in sshutil
->No suffix list.
->Making all in sshcore
->gcc -DHAVE_CONFIG_H
->-I. -I. -I../../.. -I. -I. -I../../.. -I../../..
->-I../../../lib/sshutil
->-I../../../lib/sshutil/sshcore -I../../../lib/sshutil/sshadt
->-I../../../lib/sshutil/ssholdadt -I../../../lib/sshutil/sshstrutil
->-I../../../lib/sshutil/ssheloop -I../../../lib/sshutil/sshstream
->-I../../../lib/sshutil/sshfsm -I../../../lib/sshutil/sshsysutil
->-I../../../lib/sshutil/sshnet -I../../../lib/sshutil/sshmisc
->-I../../../lib/sshutil/sshpacketstream
->-I../../../lib/sshutil/sshtestutil
->-I../../../lib/zlib -I../../../lib/sshmath -I../../../lib/sshreadline
->-I../../../lib/sshapputil -I../../../lib/sshcrypt
->-I../../../lib/sshproto
->-I../../../lib/sshagent -I../../../lib/sshsession -I../../../lib/sshhttp
->
->-I../../../lib/sshscrlock -I../../../lib/sshsmtp -I../../../lib/sshscm
->-I../../../lib/sshpgp -I../../../lib/sshipsecappapi -I../../../lib/sshhs
->
->-I../../../lib/sshexternalkey -I../../../lib/sshfilexfer -g -Wall
->-Wno-unknown-pragmas -D_OSF_SOURCE -msg_disable longdoublenyi
->-D_XOPEN_SOURCE -D_XOPEN_SOURCE_EXTENDED -cgcc
->-DHAVE_Cgcc: longdoublenyi: No such file or directory
->cc1: Invalid option `sg_disable'
->In file included from
->/usr/local/lib/gcc-lib/alphaev56-dec-osf4.0d/2.95.2/include/stdarg.h:36,
->
-> from ../../../lib/sshutil/sshincludes_unix.h:101,
-> from ../../../lib/sshutil/sshincludes.h:98,
-> from sshdebug.c:14:
->/usr/local/lib/gcc-lib/alphaev56-dec-osf4.0d/2.95.2/include/va-alpha.h:36:
->warning: redefinition
->of `va_list'
->/usr/local/lib/gcc-lib/alphaev56-dec-osf4.0d/2.95.2/include/va_list.h:7:
->warning: `va_list'
->previously declared here
->*** Exit 1
->Stop.
->*** Exit 1
->Stop.
->*** Exit 1
->Stop.
->*** Exit 1
->Stop.
->*** Exit 1
->Stop.
->
->=======================================
->
->Not sure if this is a problem with GCC libs, the Makefile changes made
->by SSH's "configure" script, or something in the SSH lib.
->
->I'm hoping this is an old problem and not new territory that I'm walking
->into. Before I jump into SSH's code, thought it would be best to check
->if anyone has a quick and dirty solution to this.
->
->TIA
->Michael
->
->
->
Michael,
I have DU4.0d patch kit 3, and had exactly the same problem you
did on my alpha 2100's. I installed gnu C compiler 2.95.2 just to install
ssh 2.1.0P12. I ended up removing the option:
`-msg_disable longdoubleenyi' from configure.in and configure. The configure
still gave me some crap about modifying those files, and the "make" had a few
warnings, but it finaly compiled.
Heres the kicker. It wont run from inetd, because it gets a "packet too long error"
even though i DID NOT build with tcpwrapper support, and when run as a daemon,
it wont fork another server after someone connects, so its unavailable to the
next user trying to connect too it. Yes, it is set to MaxConnections = 0.
So what i do is use "swatch" to look for strings in syslog to fire up another
server when needed. You need to cover regular connections, logouts, and
user disconnects.
Here are the strings that swatch looks for:
/Remote host disconnected/,/Authentication cancelled/,/RSA key generation
complete/,/ tty using TIOCSCTTY/,/Local disconnected/,/authenticated/
exec='/usr/local/sbin/sshd2 -p 22 -v'
This works for us.
Another little thing. Since we use C2 security, and this does not seem to
be built in sshd2, password authentication does not work. You have to
use publickey, create the keys on the client, and put them on the server.
I tried compiling ssh 2.2, but got the same config errors, so I will wait
until they take care of those before upgrading.
Bugs Brouillard Unix system administrator
Humboldt State Univ. 707-826-6123
Arcata, Calif.
email [EMAIL PROTECTED]
