similar to: environ problem in 3.8p1

Openssh 4.4p1 and 4.5p1 SCO Openserver 6 w/mp1, mp2 While installing v4.5p1, I noticed this sshd syslog error which began appearing when I upgraded from v4.3p2 to v4.4p1: Sep 1 17:54:41 tenzing sshd[12837]: error: Bind to port 22 on :: failed: \ Network is unreachable. sshd -d reports: debug1: Bind to port 22 on ::. Bind to port 22 on :: failed: Network is unreachable. debug1: Bind

SCO OpenServer 5.0.x Openssh 3.6p1 loginrec.c writes incorrect data into the ut_id field of the utmp file. This has been an issue since at least openssh 3.0.2 but I never bothered to report it. For Openssh 3.6p1, defining WITH_ABBREV_NO_TTY corrects the problem. Below is a brief patch to configure which does this. You can observe the errant results in the "Line" column from the

Openssh 5.5p1 and 5.6p1 SCO OpenServer 5.0.7 I've built various versions of openssh on SCO OSR5.0.7 over the years without much of a problem. Beginning with 5.5p1 however, I have been unable to get a working install. I'm building with gcc 2.95.3. The build completes normally, but 'make tests' fails on several tests: sftp-cmds.sh failures (get command fails on both): - get

openssh 4.7p1 SCO OSR6 Password authentication is non-functional. This seems dependent on USE_LIBIAF which further depends on HAVE_LIBIAF (in defines.h), but there is no longer any code in configure to define the latter. Building with HAVE_LIBIAF defined enables password authentication, but only for non-long (<9 char) passwords, even though UNIXWARE_LONG_PASSWORDS seems to be defined. I

On SCO 5.0.7 and openssh 3.8.1p1, two entries are written to /etc/wtmp and /etc/wtmpx each time a user logs in via ssh. This can be demonstrated using the last(C) command. Any user connected via ssh will have two identical login and logout entries. On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined). wtmp_write_entry()

Is anyone still using OpenSSH on SCO Open Server 3? My clients no longer run Open Server 3. The entropy gathering code changes have broken the Open Server 3 build. If there is still interest I'll work on it. If not, I have no need for it. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net

I'm not a ssh expert and I don't know if the log is good or bad, but I too am running OpenSHH under OpenServer. I find that after I connect, the return key has no effect unless I first type: stty sane <Ctrl>j If you've hit <ENTER> before that you must first press <Ctrl>j a couple of times to clean out the buffer. After I type the above command, everything

If you upgrade to sco 5.0.7, you get samba 3.0.20 5.0.6 had samba 3.0.14. so im wondering why your using samba 2.2.. samba 3.0x. is on the supplimental discs. Gr. Louis >-----Oorspronkelijk bericht----- >Van: dave at anchor-tech.co.uk >[mailto:samba-bounces at lists.samba.org] Namens David Nolan >Verzonden: vrijdag 22 mei 2015 14:12 >Aan: 'Mauricio Tavares' >CC:

Does anyone know the most up to date version of Samba that will run on SCO OpenServer 5.0.7? Kind Regards Dave Nolan Anchor Technology

Looking back in the samba mailing list archives, I see not soancient requests for samba on ancient SCO OpenServer systems. Recently faced with a situation where a Windows Server upgrade to 2012 R2 and broke an smbclient upload from a SCO OpenServer 5.0.7 system. Directory listings and file deletions did not fail, but all upload attempts produced empty files on the Windows server (this due,

Howdy, Not sure, but it appears that OpenSSH_4.3p1 on solaris creates bad wtmpx entries during login? mgoebel pts/5 Wed Dec 31 19:00 still logged in It is creating entries for Dec 31st 1969. Thanks, Matt -- Matthew Goebel : goebel at emunix.emich.edu : Unix Jockey @ EMU : Hail Eris Neo-Student, Net Lurker, Donut consumer, and procrastinating Furry Fan.

I think what I need is a prebuilt package. I currently use Samba 2.2.12 running on SCO OpenServer 5.0.6 but I am in the process of upgrading to 5.0.7. Can't move to SCO version 6 because our application isn't guaranteed to work on it. Regards Dave -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Mauricio Tavares

If SCO OpenServer is configured for large passwords, i.e. u_pwseg is greater than 1 in /etc/auth/system/default, then user authentication in auth-passwd.c will fail for users whose passwords are longer than 8 characters. The "traditional" level of security installs with u_pwseg#1, so most users would never encounter this problem. This has been an issue in openssh since I started using

Good Morning, I understand you provide support for the Samba project. I am searching for some FREE help solving what I think is a very simple problem for an experience Samba professional. I am running Samba 2.2.12 on an old SCO OpenServer 5.0.6 box. I cannot update to a more recent version of Samba as this is the last version that will run on SCO OpenServer 5.0.6. I have some

Build of 5.1p1 fails on SCO OSR6 with the error: UX:acomp: ERROR: "addrmatch.c", line 100: undefined struct/union member: sin6_scope_id configure checks for presence of struct sockaddr_in6 and uses the system declaration if found (via #define HAVE_STRUCT_SOCKADDR_IN6 in config.h) If not found, the struct is declared in openbsd-compat/fake-rfc2553.h. OSR6 has struct sockaddr_in6 but it

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

In configure for openssh 4.3p2 is this: as_executable_p="test -f" as_executable_p, as the name suggests, is used to test whether a file is executable or not, so should use -x and not -f. Discovered after doing chmod a-x gcc so configure would not discover it, but found it anyway. -- Roger Cornelius rac at tenzing.org

3.0.20 documentation bug: The smbclient's printmode command (which didn't actually do anything) has been removed in samba 3.0.20 but is still documented in the smbclient man page. -- Roger Cornelius rac@tenzing.org

I posted the message below, on the gmane.network.samba.general newsgroup some days ago, and haven't got any replies yet. If anyone has any suggestions as to what can be done, please let me know. I have been trying to use Samba 2.2.6 to print from two SCO Openserver 5.0.7 servers (VDOHOM & VDOHOM2, IP addresses 192.168.1.121 & 192.168.1.122) on a WAN consisting of networks

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