similar to: openssh-1.2.1pre24 on SCO

Yo All! I was just trying out OpenSSH 2.1.1p1 on SCO Unixware 7.1.0. The "configure" dies. See below. This seems to be the problem: if test -d "$f" -o -e "$f" ; then conf_lastlog_location=$f fi test is expecting a "shell option" after the "-o". If I run "/bin/sh ./configure" it fails. If I run "/bin/bash ./configure it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1.2.1pre25 is out. Please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html The following mirrors already have it: ftp://ftp.localhost.ca/pub/openssh/files/ ftp://thermo.stat.ncsu.edu/pub/openssh/files/ http://www.firedrake.org/openssh/files/ Changes: - - "Corrupted check bytes on input" when using triple DES has been

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1.2.1pre25 is out. Please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html The following mirrors already have it: ftp://ftp.localhost.ca/pub/openssh/files/ ftp://thermo.stat.ncsu.edu/pub/openssh/files/ http://www.firedrake.org/openssh/files/ Changes: - - "Corrupted check bytes on input" when using triple DES has been

Yo Andrew! What version of Openssh are you trying? RGDS GARY On Mon, 12 Jun 2000, Andrew McGill wrote: > Date: Mon, 12 Jun 2000 15:26:53 +0200 > From: Andrew McGill <andrewm at datrix.co.za> > To: djm at ibs.com.au > Cc: gem at rellim.com > Subject: Openssh on SCO Openserver Release 5 > > Hi there > > Your e-mail address appears in the README for openssh,

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

Hi, Does Samba supports SCO Unix (Unixware)? From the FTP sites looks like it doesn't. Regards, Mahesh -------------- next part -------------- HTML attachment scrubbed and removed

Hello list, This is a patch to rsync 2.5.5, and it serves two purposes. The small patches to batch.c, flist.c and log.c simply add "void" to some function definitions so that all declarations in proto.h have full parameter lists. unsigned char read_batch_flags() OLD unsigned char read_batch_flags(void) NEW The SCO UNIXWare compiler correctly objected to these functions not having a

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

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

I have problems installing the latest release of Samba on Caldera (SCO) Openserver 5.0.6 I have downloaded the source and ran "./configure" fine. I get an error " line 664: Syntax error " when I run "make". If I run " ./configure --with-winbind", then run "make", I get the error "Compiling smbd/server.c include/includes.h, line 885:error:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.

The do_pwchange() function in session.c needs to pass the username as an argument to the passwd command. Without it, passwd always fails with something like "passwd: unknown user" as if its getting a blank user arg. It's strange but so are many other things in SCO, which BTW was NOT my OS of choice :( To make it work I simply changed line 1317 to this: execl(_PATH_PASSWD_PROG,

Yo All! I have been playing with SSH 2.2.0 from www.ssh.com. I can not connect to openssh 2.2.1p1 using Ver 2 protocol from ssh Ver 2.2.0. Ver 1 works fine. See below for the debug output from both ends If I force hmac-md5 (-m hmac-md5) from the sender it works! The other 3 choices fail: hmac-sha1; hmac-md5-96; and none. I have no problem connecting to this openssh host (hobbes) from

ssh won't compile on this platform log: gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\" -DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" -DHAVE_CONFIG_H -c atomicio.c -o atomicio.o In file included from config.h:294, from bsd-misc.h:39, from includes.h:91,

I am trying to install openssh on sco unix 7.1 and getting following error , please help I have installed zlib - zlib-1.2.3 Openssl openssl-0.9.8e Openssh openssh-4.6p1 # make if test ! -z "yes"; then \ /usr/bin/perl ./fixprogs ssh_prng_cmds ; \ fi (cd openbsd-compat && make) cc -o ssh

In bsd-login.[hc] and login.c seems to have #include <utmp.h> that are unneeded (and platforms with non-protected headers files trips on them.) Could I get a few people on different platforms remove them and see if they cause any compiling issues it would make my life easier (and less required #ifdef grabage). bsd-login.c:52:#include <utmp.h> bsd-login.h:7:#include <utmp.h>

Yeat another test release. This fixes a few problems that were reported in the last 24 hours. One security problem fixed by this release is the braindead linking behaviour of AIX's ld. In their infinite wisdom, IBM decided to make the -L linker flag specify /runtime/ link paths. This could allow someone to substitute a modified shared library to a suid program. For gory details, have a look

Q: What platform don't run this script: ---------------------------------------- #!/bin/sh export X0='x0' export X1a="$X0/1" export X1b='$X0/1' export X2a="$X1a/2" export X2b='$X1b/2' $SHELL <<EOF_2 $SHELL <<EOF_1 cat <<EOF #define a "$X2a/aa" #define b "$X2b/bb" EOF EOF_1 EOF_2

Yo All! I understand why we do not have sftp in openssh, but it would be nice if we could make it so that when an SSH.COM scp2 client makes a connection to an OpenSSH V2 daemon that it does not hang.... Any ideas or do I need to dig a bit on this? Here is what the sshd says when I conenct to it from scp2: debug: session_open: session 0: link with channel 0 debug: confirm session debug: