similar to: Problems with sftp under SCO OpenServer (fwd)

Hello, I compiled OpenSSH 2.5.1p1 for SCO OpenServer 5.0.5, HPUX B.11.00, and SunOS 5.7. When I sftp into the HP or Sun box, everything works fine. However, whenever I sftp into the OpenServer box, all remote filenames are shown as "(null)". File sizes, owners, etc. display properly. This behavior is exhibited from all origination points. OpenSSH was configured with identical

Hi All, I've seen the various reports about the problems logging out under Solaris. I can duplicate this under both Solaris 7 and 8 (sparc). I've also noticed another behavior, though. Anytime I press Ctrl-C while connected to a Solaris system running the 3.2.2 server, the session completely disconnects. This only appears to be happening with Solaris, as tests under SCO OpenServer and

Hi All, I've been having issues getting X forwarding to work on OpenServer for OpenSSH versions 3.4p1 and 3.5p1. I have compiled OpenSSH on Redhat Linux 8.0, Solaris 8, and OpenServer 5.0.6, but the OpenServer box is the only one that exhibits the problem. I've detailed everything below. I am using PuTTY for my ssh client under Windows. If I connect to the Linux or Solaris boxes, X

Dears Sirs; I'm tryng to compile and install samba 3.0.14a on a SCO Openserver 5.0.6 server (i want to use some shared printers from MS server2003 on a customer network, but with samba SCO ver 2.2, i can't obtain the authorization from the domain controller to use shared resources), but i'm havig a lot of trouble. I had dowloaded samba-3.0.14a.tar.gz fro Samba.org. I had put all the

Whoever can help me... pls find attached the loggings for the openssh sessions from local(host=keg;redhat linux) to remote (host=ben;lynxos) The issue is when I run sshd in debug mode and try to logon from local, password authentication succeeds, but if I run sshd as a daemon, it fails. sshlocal.txt >>> logging at local when sshd is not run with debug option sshlocal...txt >>

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

On Fri, May 22, 2015 at 8:31 AM, L.P.H. van Belle <belle at bazuin.nl> wrote: > 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 Been there, done that. Samba 2.2 was built into the base release, supplements weren't always stable or well

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

On Wed, Sep 12, 2018 at 03:27:37PM -0500, Kevin R. Bulgrien via samba wrote: > 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

I downloaded the Openssh-2.3.0p1 file and ran configure only to have it fail reporting the lack of libz. I found that configure was failing beacuse the test program did not include the libtinfo and libm which are needed to resolve references in libprot. I made changes to the configure script to add those libraries for SCO Openserver and then tried to compile the programs only to run into another

Hi All, I compiled the 3.2.3p1 source on SCO OpenServer 5.0.6. When a client connects to it now, they get stair-stepping everywhere. Issuing an stty sane resolves the issue for that login. For bug 245 in 3.2.2p1, the call to setsid() is sshd.c was bypassed due to problems it was causing with Solaris. However, by allowing this method to be called, the stair-stepping goes away. Thanks, Greg

I just finished compiling openssh-2.1.0p3 on a SCO openserver system. I generated the keys fine and genereated the host keys both rsa and dsa without problems. ssh (version1) works great. I tried to use ssh (version 2) and after being prompted to login, it quits. I am attaching a script file of... ssh -v -2 root at sco to see if you can find the problem. Let me know how I can help. [root at

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

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.

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

You can download Ncurses for SCO OpenServer via ftp://ftp2.caldera.com/pub/skunkware/osr5/vols/ncurses-4.2-VOLS.tar This is a tar archive of media images suitable for installation with the SCO Software Manager (/etc/custom). Cheers, Ron Record rr@sco.com re: > Date: Wed, 26 Feb 2003 15:54:59 +0000 > From: Simon Hobson <shobson-lists@colony.com> > To: samba@lists.samba.org >

okay, i reversed that patch out and solaris 7 still works fine with pam... devon ----- Original Message ----- From: <mouring at etoh.eviladmin.org> To: <devon at admin2.gisnetworks.com> Sent: Thursday, February 22, 2001 10:43 AM Subject: Re: Solaris and Latest snapshot (2001-02-21) (fwd) > > > ---------- Forwarded message ---------- > Date: Wed, 21 Feb 2001 17:54:19

On 09/12/18 16:56, Jeremy Allison via samba wrote: > On Wed, Sep 12, 2018 at 03:27:37PM -0500, Kevin R. Bulgrien via samba wrote: >> 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

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:

Hi Chris I made it installing the KDE/KDevelop (SCO Skunkware), but when the configure find gcc, exit with a lot of errors without producing the Makefile! Any idea? Thanks > > I have installed the development package (SCO) on my machine so > > now i have cc. > > Why don't you try to find gcc instezad of using SCO's cc? > > --- > Chris Covington > IT >