similar to: This is what I get when I try to install openssh

Hi Damien, I have a problem getting openssh-2.9p2 properly configured. This is the problem: configure:4433: gcc -o conftest -g -O2 -Wall -I/opt/openssl/include -L/opt/open ssl/lib conftest.c -lz -lnsl -lutil -lcrypto 1>&5 /opt/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load': dso_dlfcn.o(.text+0x8e): undefined reference to `dlopen' dso_dlfcn.o(.text+0xa4):

xlc -O2 -qmaxmem=-1 -qarch=com -I/opt/TWWfsw/tcpwrap/include -I. -I.. -I. -I./.. -I/opt/TWWfsw/libopenssl09s/include -I/opt/TWWfsw/zlib11s/include -DHAVE_CONFIG_H -c glob.c "glob.c", line 100.9: 1506-213 (S) Macro name TILDE cannot be redefined. "glob.c", line 100.9: 1506-358 (I) "TILDE" is defined on line 250 of /usr/include/sys/ioctl.h. gmake[1]: *** [glob.o] Error

Hello. Installed OpenSSL-0.98 I cannot collect new OpenSSH-4.2p1 at assembly there is a mistake: if test ! -z ""; then \ /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; \ fi (cd openbsd-compat && make) make[1]: Entering directory `/home/pkg/openssh-4.2p1/openbsd-compat' make[1]: ???? `all' ?? ??????? ?????????? ??????. make[1]: Leaving directory

Hi there, I have tried compiling OpenSSH 4.3p2 using the following steps: Upgrade OpenSSL tar xvfz openssl-0.9.8a.tar.gz cd openssl-0.9.8a ./config make make install Upgrade zlib tar xvfz zlib-1.2.3.tar.gz ./configure make test make install Upgrade OpenSSH tar xvfz openssh-4.3p2.tar.gz cd openssh-4.3p2.tar.gz ./configure --with-tcp-wrappers --with-ssl-dir=/usr/local/ssl

Openssh gurus, On Suse Linux 9.3 using kernel 2.6.11.4-21.9-default, x86_64 system with an athlon64: If I make openssh 4.2p1 using the system's default ssl 0.9.7e, all is well; however, make fails if I install the newer ssl 0.9.8 and configure openssh with: ./configure --with-ssl-dir=/usr/local/ssl A snippet from the last output from make is: _PATH_SSH_PIDDIR=\"/var/run\"

When trying to make the last version I'm getting this error (#./configure --prefix=/some/dir); #make): ============================ gcc -g -O2 -I/usr/local/openssl/include -DPKGLIBDIR=/usr/local/tinc_new/lib /tinc -DCONFDIR=\"/usr/local/tinc_new/etc\" -DLOCALEDIR=\"/usr/local /tinc_new/share/locale\" -DLOCALSTATEDIR=\"/usr/local/tinc_new/var\" -o tincd

A trailing comma in an enum generates an error with the IBM C compiler, xlc, on AIX 4.3.2: $ gmake ... xlc -O2 -qmaxmem=-1 -qarch=com -I/opt/TWWfsw/tcpwrap/include -I. -I. -I/opt/TWWfsw/libopenssl09s/include -I/opt/TWWfsw/zlib11s/include -DSSHDIR=\"/etc/opt/TWWfsw/openssh323\" -D_PATH_SSH_PROGRAM=\"/opt/TWWfsw/openssh323/bin/ssh\"

http://bugzilla.mindrot.org/show_bug.cgi?id=266 Summary: Trailing comma in enum for 3.2.3p1 Product: Portable OpenSSH Version: -current Platform: PPC URL: ftp://ftp.thewrittenword.com/outgoing/pub/openssh- 3.2.3p1-2.patch OS/Version: AIX Status: NEW Severity: normal Priority: P2

http://bugzilla.mindrot.org/show_bug.cgi?id=267 Summary: Build problems with 3.2.3p1 under Tru64 UNIX 4.0D Product: Portable OpenSSH Version: -current Platform: Alpha URL: ftp://ftp.thewrittenword.com/outgoing/pub/openssh- 3.2.3p1-3.patch OS/Version: OSF/1 Status: NEW Severity: normal

http://bugzilla.mindrot.org/show_bug.cgi?id=265 Summary: Build problems with 3.2.3p1 under AIX 4.3.2 Product: Portable OpenSSH Version: -current Platform: PPC URL: ftp://ftp.thewrittenword.com/outgoing/pub/openssh- 3.2.3p1-1.patch OS/Version: AIX Status: NEW Severity: normal

Tru64 UNIX 4.0D, with the DTK (Desktop Toolkit), includes int64_t in /usr/include.dtk/stdint.h. $ gmake ... (cd openbsd-compat && gmake) gmake[1]: Entering directory `/opt/build/openssh-3.2.3p1/openbsd-compat' cc -O2 -std -I/opt/TWWfsw/tcpwrap/include -I. -I.. -I. -I./.. -I/opt/TWWfsw/libopenssl09s/include -I/opt/TWWfsw/zlib11s/include -DHAVE_CONFIG_H -c bsd-arc4random.c cc: Error:

On IRIX 6.5: cc -Wl,-woff,84 -Wl,-woff,85 -woff 1429 -O2 -I/opt/TWWfsw/tcpwrap/include -I. -I.. -I. -I./.. -I/opt/TWWfsw/libopenssl097s/include -I/opt/TWWfsw/zlib11s/include -DHAVE_CONFIG_H -c inet_ntoa.c cc-1035 cc: WARNING File = /usr/include/stdint.h, Line = 5 #error directive: This header file is to be used only for c99 mode compilations #error This header file is to be used

http://bugzilla.mindrot.org/show_bug.cgi?id=251 Summary: openssh-3.2.2p1-1.src.rpm won't build under RH6.2 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=307 Summary: configure fails to add -ldl (RedHat specfile) Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

Hello guys. Following Dug's withdrawal of the SSH1 AFS patches, I'm trying to give OpenSSH installation another shot. It fails. The setting: * Platforms: Linux (Immunix 6.2), Solaris 7, IRIX 6.5, OSF1 4.0F, HP-UX 10.20. * Compilers: StackGuard egcs on Linux, vendor-supplied native on others (Workshop 5.0 Sun; MIPSpro 7.3 SGI; OSFCMPLRS440 package; HP ANSI C compiler B3899BA

In S(plus), I can write functions using code fragments like if(!is.loaded(symbol.C("my_C_fun"))) dyn.load("......../my_C_fun.o") r <- .C("my_C_fun", x = x, n = n, ... ) which I would like to have in R, too. The S-plus help page on this subject says : S+>> Code Availability S+>> S+>> DESCRIPTION: S+>> is.loaded

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

Howdy, After upgrading to 2.9 (OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f) I'm unable to ssh between two systems any more (the two that I've upgraded). I've recompiled from the original source several times, each time with no errors, regenerated host keys, regenerated client keys (using rsa), etc., to no avail. Below are some relevant snippets of debugging output

No response yet, so resending. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords ---------- Forwarded message ---------- Date: Fri, 12 Oct 2001 09:44:54 +0300 (EEST) From: Pekka Savola <pekkas at netcore.fi> To: Damien Miller

Hi! I am distributing 2.5.1p1 for production use on my system by now and prepare switching to protocol 2 as default protocol. I just noted, that ssh-agent can be used for protocol 1 and 2, but the keys kept in ssh-agent are not compared against keys in .ssh. Example: I have a DSA key in id_dsa which I load into ssh-agent on login. When connecting to an account accepting the key everything is