similar to: autoconf-2.62

While the changes to m4/nut_check_libssl.m4 have improved detection of OpenSSL on Solaris, it breaks on platforms that did not have pkg-config from the vendor. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net

If nobody objects within 24 hours, I will tag and release 2.4.2-pre1. cheers, Arnaud

Greetings: On a Sun Solaris 8 machine using the Sun Studio 11 compiler: taz$ ./configure LDFLAGS=-xarch=v9 CFLAGS='-xO3 -xarch=v9' CC=/opt/SUNWspro/bin/cc --prefix=/opt/openssh-4.3p1 --with-ssl-dir=/opt/openssl-0.9.8a --with-xauth=/usr/openwin/bin/xauth --with-default-path=/bin:/sbin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/openwin/bin:/usr/dt/bin --without-zlib-version-check checking

Hi, I have ported OpenSSH-4.0p1 to UnixWare 7.1.4. Can you please add the following for UnixWare 7 in the configure script: Description: + cross compiler produces i386a.out. + libcrypt which needs to come after openssl's libcrypto. + passwd needs user name. Thanks, Ahsan Rashid --- openssh-4.0p1/configure Tue Mar 8 23:54:16 2005 +++ dist/configure Thu Apr 14 17:09:54 2005 @@ -1728,7

I have been asked to investigate the use of OpenSSH on some of our systems. These systems are running SCO OpenUnix ( Unixware 7.1.2). Are you aware of any issues that may prevent me from using OpenSSH on this version of SCO. Thank you Andrew Harasymiw Senior Technical Analyst Shoppers Drug Mart Office: (416) 493-1220 Ext: 5225 Cell: (416) 553-4616 Email: aharasymiw at

I have attached two patches to the current source code. The first addresses the pty problems with UnixWare 2.x with connecting with SSH2. It sets the sigaction to SA_RESTART. This fixes UnixWare v2.x, but haven't heard any feedback as to effects on other OS'. The first patch is against misc.c. The second patch adds a section "*-*-sysv4.2uw2*" to configure to set the

No "ssh -X hostname" doesn't work. But when you "export DISPLAY=..." it works!? I set the the Display Hack so that I can see my IP with "env" or "echo SSH_CLIENT" when I'm connect via VPN-Tunnel and I don't know my IP in the Net I'm connected through. Andreas Kerl ----------------------------------------- DTS Medien GmbH Heidestrasse 38

I am building version 2.3.0p1 of openssh on a UnixWare 2.03 system and am unable to connect with SSH 2. The error I get is: debug: len 55 datafellows 0 debug: dsa_verify: signature incorrect dsa_verify failed for server_host_key The build environment is as follows: gcc 2.95.1 openssl-0.9.6-beta2 I've looked through the archives and found similar problems related to version

I read the exchange regarding > 8 char passwords on Unixware from the end of June. Is anything being done to add support for >8 character passwords on SCO OSR6 (in udk mode)? I have it working by calling osr5bigcrypt(), instead of bigcrypt(), in openbsd-compat/xcrypt.c and linking with -lcrypt. libcrypt has bigcrypt(), but for whatever reason, openssh built with it fails to authenticate

All, How can I get at the daily snapshots? When I go to the website, www.openssh.com, and follow the Linux link to portable.html and then go to request the daily snapshot from http://bass.directhit.com/openssh_snap/, I get prompted for a user id and password. Needless to say, I ain't got. That's real useful. Use to be, I could get the snapshots from the ftp site. Then things

Anyone have any problems with sftp-server on 3.7.1p2? When I sftp to the server i get this when I do an ls -l: sftp> ls -l ?-w-rwxrwx 0 1 16832 3 Oct 26 1993 Mike

I wasn't sur if you're the right person to send the bug reports to... SCO Unixware 7.1.0 (uname: UnixWare) and probably the 2.1.x versions (uname: UNIX_SV) requires also to have USE_PIPES defined. Also when compiling with tcpwrap it doesn't link due to the fact that UW doesn't have setenv() and libwrap have one built-in (duplicate symbols)... Also when using the SSH2 protocol to

Hello, I ran into a few problems when trying to build openssh 5.2p1 on IRIX 5.3. First one is new to 5.2p1: cc -I. -I. -I/usr/tgcware/include/openssl -I/usr/tgcware/include -DSSHDIR=\"/usr/tgcware/etc/ssh\" -D_PATH_SSH_PROGRAM=\"/usr/tgcware/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/tgcware/libexec/ssh-askpass\"

openssh-2.9.9p2/configure.in says: # Disabled until it works on SCO and HPUX #AC_SYS_LARGEFILE As an autoconf maintainer I'd like to fix this. Can you please explain what's broken on SCO and HPUX? I'm puzzled by the comment, as AC_SYS_LARGEFILE is a feature introduced in autoconf 2.50, whereas openssh-2.9.9p2/configure was built with autoconf 2.13. Anyway, some older GNU

Greetings, I recently discovered a problem with OpenSSH 3.6.1p2 and UnixWare 7.1.1 (as well as OpenServer 5.0.X and SCO 3.2v4.2) When I set up sshd_config as follows: PasswordAuthentication no PermitEmptyPasswords yes and try to connect to a password less account ( I know its a F*up, but that's the application ID10Ts .... ) I can get in using the SSH2 version without a valid key, the

On Irix 6.5.15m with version 7.3 of the development tools, monitor_fdpass.c won't compile after a normal configure because SCM_RIGHTS isn't defined. In sys/socket.h it's protected by #ifdef _XOPEN_SOURCE but if I define _XOPEN_SOURCE, I get a storm of IPV6-related errors. Defining SCM_RIGHTS explicitly does allow it to build. I can't immediately figure out how to fix this

Hi If I try to run configure for openssh-5.1p1 with --wtih-selinux option it fails giving the error "selinux support requires selinux library" all of the below also dont work a) --wtih-selinux b) --wtih-selinux=path of cross complied library c) LDFLAGS=-Lpath of cross complied library if I remove --wtih-selinux option I am able to everything is fine. How to solve this error? Thanks

Hi, This is included in the release now; any feedback? Privilege separation, or privsep, is method in OpenSSH by which operations that require root privilege are performed by a separate privileged monitor process. Its purpose is to prevent privilege escalation by containing corruption to an unprivileged process. More information is available at:

I think we need to revisit the whole 64bit integer support. It has crept from sftp over to scp now. And I think we are at a point where [..] # If we don't have int64_t then we can't compile sftp-server. So don't # even attempt to do it. if test "x$ac_cv_have_int64_t" = "xno" -a \ "x$ac_cv_sizeof_long_int" != "x8" -a \

Actually it really never was answered, but here's how I fixed (worked around) it. At first I thought installing patch PHNE_27796 (libnss_dns DNS backend patch) had fixed it. It didn't. It just flip-flopped the problem. Prior to installing that patch, ssh would never go to DNS no matter what was in nsswitch.conf. It appeared to only look in /etc/hosts. After installing the patch, ssh