similar to: 3.6p1 bug on SCO OpenServer

These issues affected previous 2. versions of openssh and still affects openssh-2.1.1p1. The environment is SCO OS 5.0.5 with the SCO development environment (not gcc, gmake, etc.) There are two issues, the first is a compilation problem, and the second is a run-time problem. The first problem is simply that MAXPATHLEN is not defined. I found it to be defined in

Simon Cooper already mailed in a patch to get the effects of MAP_ANON on IRIX systems, but it was against openssh/3.3p1. I've reapplied his patach to openssh/3.4p1 and include it as an attachment. Here's his explanation: > I noticed that the recent release requires the existence of MAP_ANON to get > an anonymous memory region. In Irix the equivalent functionality can be >

shell# /sbin/devfs rule -s 2 delset shell# /sbin/devfs rule -s 2 add hide shell# /sbin/devfs rule -s 2 add path random unhide shell# /sbin/devfs rule -s 2 add path urandom unhide shell# /sbin/devfs rule -s 2 add path zero unhide shell# /sbin/devfs rule -s 2 add path pty\* unhide shell# /sbin/devfs rule -s 2 add path pty\* unhide shell# /sbin/devfs rule -s 2 add path tty\* unhide shell#

Hi, I've seen a few messages re. problems with 3.7.1p1 on IRIX 6.5... I'm using 6.5.19 and having no trouble compiling, installing and starting, but sshd just closes the connection with no explanation. debug/verbose modes don't seem to give any clues. Darren Tucker suggested defining BROKEN_GETADDRINFO in config.h, but I find that compilation then fails (assuming I've implemented

Details of installation attached. Effect: when I build and test (with full path names) ssh in the openssh... directory, everything works fine. When I "install" it as per attached file into a test-directory and run it from there, there are 2 phenomena: either it just hangs, eating 96% of CPU or it dies with a Segmentation fault (this is what happens most often) Help needed

I apologize if this has been reported already - my company has blocked the reporting site so I cannot see if it has or what the solution is. I have also reported this to AT&T as a UWIN issue too. Ok - so I am running UWIN 4.1 (the latest version of this) on a Windows XP SP2 system. UWIN 4.1 bundles with it OpenSSH 3.6p1. I have setup and tested SSH and it works fine. I can run an

IRIX 6.5 has the basename() function in libgen. SYNOPSIS cc [flag ...] file ... -lgen [library ...] #include <libgen.h> char *basename (char *path); -- ayamura

Hi list, I just upgraded an AD DC from 4.1.17 to 4.2.10 (using jessie package), wbinfo -r someuser now fails randomly (well not THAT randomly I guess it depends on group membership) $ wbinfo -r oneuser failed to call wbcGetGroups: WBC_ERR_DOMAIN_NOT_FOUND Could not get groups for user oneuser $ wbinfo -r anotheruser [list of GIDs] wbinfo -u & wbinfo -g returns no error wbinfo -i oneuser

I never have had a problem compiling Samba until 2.2.2 after installing a SCO patch 506a on OpenServer 5.0.6. I noticed the following message when running configure that does not normally appear: WARNING: No automated network interface determination make output: Using FLAGS = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -DLOGFILEBASE ="/usr/local/samba/var"

Hi all, I'm writing to you becuase I have compiled PAM in SCO (now Caldera) Openserver 5.0.x, and when I tried to use SSH with PAM enabled, y realized that OpenSSH depends on the user to exist en the /etc/passwd, and /etc/shadow databases, or equivalent ones (it uses getpw...() functions to determine validity of the user). In Linux, the simlpe solution is to use nsswitch, but it seems to hard

Hello, after one small modification I was able to compile samba. I have not yet tried to use it, but at least swat is working. It would be nice if anyone could modify the current code to resolve the specified problems. Mike The Problems: Only a nuisance: uid_t and gid_t are unsigned: /GNU-Source/samba-2.2.0-alpha1/source/smbd/sec_ctx.c: In function `initialise_groups':

Hello, We are trying to compile the samba 2.2.0-alpha3 source on a SCO Openserver 5.0.6 server. we ran configure with standard options no visible problems. On running make we get the following error ..... Compiling tdb/spinlock.c Compiling tdb/tdbutil.c Compiling printing/printing.c Compiling printing/nt_printing.c Compiling smbd/noquotas.c Compiling smbd/oplock.c Compiling smbd/oplock_irix.c

James A. Mutter wrote: >Does anyone know of any issues with 2.0.5 and SCO Openserver 5.0.5? A >friend told me that he had "real problems", but couldn't elaborate. >Is there something I should be aware of before I try this? >Thanks, >Jim Hi, As far as I know there are no problems with running Samba on a SCO system, beside the normal Samba configuration problems.

Hi folks, I'm trying to install OpenSSH 2.3.0 on a SCO OpenServer Release 3.2 v.5.0.5 box. I downloaded the tarball from the 'portable' directory and uncompressed. ./configure --with-egd-pool=/dev/random <-- works with no errors. Output attached here: (See attached file: output.txt) make displays: root:/tmp/OpenSSH/openssh-2.3.0p1 # make cc -g -I. -I.

This is the final results of sftp on SCO OpenServer. ---------- Forwarded message ---------- Date: Mon, 26 Feb 2001 12:27:51 -0700 From: Greg Jewell <gjewell at cnnxn.com> To: mouring at etoh.eviladmin.org Subject: RE: Problems with sftp under SCO OpenServer > -----Original Message----- > From: mouring at etoh.eviladmin.org [mailto:mouring at etoh.eviladmin.org] > Sent: Monday,

Hello, There appears to be a display issue when connecting to an OpenServer system using SSH2. I've compiled OpenSSH 2.5.1p1 on SunOS 5.7, HP-UX 11, and OpenServer 5.0.5. Whenever the destination is the OpenServer system, the display has a step-ladder effect. This behavior exhibits itself no matter what box the origination point is. A quick inspection revealed that the stty settings of

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

Has anyone got privsep to work under SCO Openserver? I am testing openssh3.3p1. I have Compression turned off in sshd_config. Here is the error messages that I am getting. sshd[21469]: fatal: mm_send_fd: sendmsg(3): Bad file number sshd[21476]: fatal: mm_receive_fd: recvmsg: expected received 1 got 0 --Sam

Does anybody here have experience running SCO OpenServer 5.0.6a or earlier under KVM? Bill -- INTERNET: bill at celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax: (206) 232-9186 Skype: jwccsllc (206) 855-5792 Under democracy one party always devotes

I'm using the O'Reilly's Using Samba book to try and get Samba to send UNIX (OPENSERVER 5) data to a printer connected to a Windows XP machine and having some trouble. I've edited the /etc/printcap and /var/spool files as stated in the book but I can't seem to get my UNIX system to see that the printer is there. Do I add the printer somewhere other that the GUI install area