similar to: SCO 5.0.5 (i686-pc-sco3.2v5.0.5), scp and the -n option

Displaying 20 results from an estimated 4000 matches similar to: "SCO 5.0.5 (i686-pc-sco3.2v5.0.5), scp and the -n option"

2002 Mar 12
3
error compiling openssh-3.1p1 under SCO OpenServer 5.0.5
Trying to compile openssh-3.1p1 on SCO using: export CCFLAGS='-L/usr/local/lib -I/usr/local/include' ./configure --sysconfdir=/etc/ssh --with-rsh=/usr/bin/rcmd --exec-prefix=/usr OpenSSH has been configured with the following options: User binaries: /usr/bin System binaries: /usr/sbin Configuration files: /etc/ssh Askpass
2010 Nov 05
2
test request: SCO with setluid() (i686-pc-sco3.2v5.0.7, possibly others)
Hi all. I am cleaning up (I hope) one of the nastier pieces of code in openssh: do_setusercontext which is/was a twisty maze of platform-specific nested ifdefs. I made a series of changes[1] where I moved each platform-specific piece into a portable-only file platform.c, which does not need to be kept in sync with OpenBSD. The changes did not (I hope!) change the semantics, but there's one
2005 Feb 26
1
drop support for SCO 3.2v4.2
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
2000 Jun 15
1
SCO OpenServer 5.0.5, issues with MAXPATHLEN and tty devices
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
2001 Jun 13
1
2.9p1 SCO OS 5.0.5 server and Linux client hang on exit when using X11 forwarding and protocol 2
When I run this command: ssh -1 -v -n -l root njdb1b /usr/bin/X11/xterm -sb -sl 1000 -T njdb1b -e find /etc An xterm appears on my screen, the contents of /etc scroll by and then ssh exits. When I invoke the same command with the -2 option, the xterm appears (and disappears) but ssh never exits. netstat says the (ssh) connection is still established but the xterm is no longer
2001 Feb 12
1
OpenSSH 2.3.0p1 bug with SCO UnixWare 7.1.0
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
2001 Feb 12
3
add scp path to _PATH_STDPATH
what do you think about this patch to add the path to scp to _PATH_STDPATH? is there a better or cleaner way to do this? i'm hoping to ward off 'scp doesn't work' questions for the next release. i did *not* add this to a --with-default-path path, because if a user specifies that, they should control its value completely. Index: Makefile.in
2000 Nov 15
0
2.3.0p1 + Sco3.2v5.0.5
> ---------- Forwarded message ---------- > Date: Tue, 14 Nov 2000 22:00:41 +1000 > >From: Robert Brady <robert at crow.cfs.net.au> > To: openssh at openssh.com > Subject: 2.3.0p1 + Sco3.2v5.0.5 > > Hi, > I'm trying to build openssh 2.3.0p1 on sco openserver 5.0.5. > configure is failing as shown below. > Version 2.2.0p1 build and runs OK > >
2000 Nov 09
2
SCO Openserver Patch
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
2002 Mar 12
2
sys/queue.h
removes HAVE_BOGUS_SYS_QUEUE_H and always use our queue.h. ok? Index: acconfig.h =================================================================== RCS file: /var/cvs/openssh/acconfig.h,v retrieving revision 1.122 diff -u -r1.122 acconfig.h --- acconfig.h 26 Feb 2002 16:40:49 -0000 1.122 +++ acconfig.h 12 Mar 2002 02:11:39 -0000 @@ -14,7 +14,6 @@ /* SCO workaround */ #undef
2000 Nov 14
0
2.3.0p1 + Sco3.2v5.0.5 (fwd)
-- | ``We've all heard that a million monkeys banging on | Damien Miller - | a million typewriters will eventually reproduce the | <djm at mindrot.org> | works of Shakespeare. Now, thanks to the Internet, / | we know this is not true.'' - Robert Wilensky UCB / http://www.mindrot.org ---------- Forwarded message ---------- Date: Tue, 14 Nov 2000 22:00:41 +1000 From: Robert
2003 Sep 05
2
3.6p1 bug on SCO OpenServer
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
2011 Jun 30
4
sshd and .bashrc
The short version: There's a "#define USE_PIPES" in the middle of session.c; it would be better if it were in (e.g.) defines.h or some other .h file. (If in fact it needs to be defined at all; I'm not convinced that it does.) Here's the (much) longer version: I recently installed the latest OpenSSH on some of our servers (RHEL5, which provides the 4.3 release) and soon
2000 Jul 03
1
Antwort: Re: sshd does not exit after scp (hpux 11.00 / ssh 2.1 .1p1)
Hi, stevesk at sweden.hp.com wrote: > Has any progress been made on this issue? I've included an older > message that has a stack trace, which if I recall was still the same in > 2.1.1p1. I can provide a newer trace or additional information if > needed. not really... On a non-trusted system with HP AnsiC it seems to work if changing shutdown(fdin, SHUT_WR) to shutdown(fdin,
2001 Feb 20
1
_PATH_STDPATH and @bindir@
Sorry if this is stuff that's been talked about before. If it is, just ignore me. I'm curious to know why Portable OpenSSH doesn't include @bindir@ in the _PATH_STDPATH. This would save most installers of portable OpenSSH from having to --with-default-path=$PREFIX/bin in order to ensure that scp will work properly. This would also, I imagine, save quite a lot of hassle for
2001 Jul 03
2
2.9p?: connection hangs with agent forwarding
Hi! when using agent forwarding, the connection hangs on exit, if the agent has been accessed. Symptoms: - On the client side, when the agent is accessed, the following output is being logged: debug1: channel 1: new [authentication agent connection] debug1: confirm auth-agent at openssh.com debug1: channel 1: rcvd eof debug1: channel 1: output open -> drain debug1: channel 1: obuf empty
2001 May 16
1
[PATCH]: configure.in
Hi, it would be nice if somebody could apply the following patch. After some months of maintaining the Cygwin version of OpenSSH it finally turned out that USE_PIPES is the better option for Cygwin. It's working more reliable than socketpairs and it's WAY faster. Index: configure.in =================================================================== RCS file:
1999 Sep 22
0
SAMBA digest 2243 / 2.0.5 and SCO Openserver 5.0.5
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.
2000 Jan 26
0
SAMBA digest 2391 / Samba 2.0.6 on SCO Unix 5.0.5
Denis Caron wrote: >>We seem to be experiencing some problems with Samba 2.0.6 on SCO Unix >>Openserver 5.0.5. >> >>I'm wondering if anybody else is using this version of Samba on SCO. I used >>an older version 3 years ago and rarely had a problem. I just installed this >>version and am experiencing an annoying problem: >> >>We use
2000 Jan 26
0
Samba 2.0.6 on SCO Unix 5.0.5
We seem to be experiencing some problems with Samba 2.0.6 on SCO Unix Openserver 5.0.5. I'm wondering if anybody else is using this version of Samba on SCO. I used an older version 3 years ago and rarely had a problem. I just installed this version and am experiencing an annoying problem: We use windows 95, 98 and NT4.0 (SP3/SP6) workstations. All passwords are set to clear text. The samba