similar to: SSL test regression

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

It looks like the change to m4/nut_check_libnetsnmp.m4 in r1968 broke the test on at least Solaris 10. Here is one possible fix. ---------------------------- --- m4/nut_check_libnetsnmp.m4.old 2009-12-15 09:30:48.000000000 -0800 +++ m4/nut_check_libnetsnmp.m4 2009-12-15 11:12:15.291295000 -0800 @@ -9,7 +9,8 @@ if test -z "${nut_have_libnetsnmp_seen}"; then

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

On Fri, Feb 12, 2010 at 5:35 PM, Tim Rice <tim at multitalents.net> wrote: > Attached as cofig.log.gz and compile.log.gz I saw a few warnings: > "/opt/src/utils/nut-2.4.1-r2339/drivers/apcsmart.c", line 34: warning: too many struct/union initializers > "/opt/src/utils/nut-2.4.1-r2339/drivers/apcsmart.c", line 44: warning: too many struct/union initializers >

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

I ran into a portability issue with drivers/bcmxcp.c in nut-2.4.1 on my UnixWare 7.1.4 machine. The error I get is ..... UX:acomp: ERROR: "/opt/src/utils/nut-2.4.1/drivers/bcmxcp.c", line 835: integral constant expression expected ..... Looking at the code we see ..... int init_outlet(unsigned char len) { unsigned char answer[len]; ..... Although gcc can handle it, it's not

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

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

ChangeLog 20001230 - (bal) if no MAXHOSTNAMELEN is defined. Default to 64 character defination. Suggested by Christian Kurz <shorty at debain.org> This change causes compiler warnings on UnixWare 7, Solaris 7, others? ... gcc -g -O2 -Wall -I/usr/local/include -I/usr/local/ssl/include -I. -Isrc -DETCDI R=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\"

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

I put together a nanosleep() for systems without it. Please review/test before I commit. It sems to make UnixWare and Open Server 5 happy. My SCO Open Server 3 box broke so I can't test it there. -------------< cut here >---------------- --- openssh/configure.ac.old 2003-03-09 17:16:43.000000000 -0800 +++ openssh/configure.ac 2003-03-16 15:38:28.520560008 -0800 @@ -1483,6 +1483,8 @@

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

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 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

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

It looks like host based authentication will not work if you attempt to set EnableSSHKeysign on a per host basis. Ie. This does not work. ------- Host ou8 HostName ou8.somedomain.com HostbasedAuthentication yes EnableSSHKeysign yes NoHostAuthenticationForLocalhost yes ------- Unless you also add ----- Host * EnableSSHKeysign yes ----- Is this the intended behavior? -- Tim Rice

There was a patch merged in on 9/29 that changed remove() calls to unlink(): - (djm) Merged big SCO portability patch from Tim Rice <tim at multitalents.net> Does SCO's libc not include remove()? Note that sftp-server.c is currently using remove. The reason I ask is I'd like to keep the portable tree as close to openbsd as possible, and if we need remove() for SCO we should

I've had the wrong sshd daemon killed by "killing using alternate method" too many times. Would this cause anyone any grief? --- opensshd.in.old Sun Oct 21 16:42:02 2001 +++ opensshd.in Mon Jul 15 19:34:16 2002 @@ -3,11 +3,8 @@ # # Stripped PRNGd out of it for the time being. -AWK=/usr/bin/awk CAT=/usr/bin/cat KILL=/usr/bin/kill -PS=/usr/bin/ps -XARGS=/usr/bin/xargs

I'm considering commiting something like this. -------------------------------- --- configure.ac.old 2005-02-24 19:47:25.361190001 -0800 +++ configure.ac 2005-02-25 12:33:35.341390018 -0800 @@ -374,23 +374,7 @@ ;; # SCO UNIX and OEM versions of SCO UNIX *-*-sco3.2v4*) - CPPFLAGS="$CPPFLAGS -Dftruncate=chsize" [snip next 16 deleted lines] + AC_MSG_ERROR("This Platform