Displaying 20 results from an estimated 300 matches similar to: "SCO 5.0.5 setluid patch"
2001 Feb 08
5
Daily snapshots...
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
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
2002 Jun 25
3
BSD/OS with privsep
I need this for BSD/OS 4.2 + privsep
perhaps we should not call do_setusercontext() after
chroot().
--- sshd.c.orig Fri Jun 21 03:09:47 2002
+++ sshd.c Tue Jun 25 13:11:03 2002
@@ -548,21 +548,35 @@
/* Change our root directory*/
if (chroot(_PATH_PRIVSEP_CHROOT_DIR) == -1)
fatal("chroot(\"%s\"): %s", _PATH_PRIVSEP_CHROOT_DIR,
strerror(errno));
if
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
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 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
2007 Sep 10
1
4.7p1 password auth broken on SCO OSR6
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
2003 Dec 30
8
[Bug 651] SCO 3.2v4.2 and OpenSSH 3.7.1p1 --> connection hangs and does not close (ssh2 only)
http://bugzilla.mindrot.org/show_bug.cgi?id=651
------- Additional Comments From vikashb at comparexafrica.co.za 2003-12-30 16:39 -------
tried openssh-SNAP-20031223
does not compile:
(cd openbsd-compat && make)
gcc -g -O2 -Wall -Wpointer-arith -Wno-uninitialized -I. -I.. -I. -I./..
-I/usr/local/ssl/include -Dftruncate=chsize -I/usr/local/include
-DHAVE_CONFIG_H -c
2005 Sep 19
1
ssh hangs or gives Segmentation fault
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
2002 Jul 04
4
Chroot patch (v3.4p1)
The following is a patch I've been working on to support a "ChrootUser"
option in the sshd_config file.
I was looking for a way to offer sftp access and at the same time restict
interactive shell access. This patch is a necessary first step (IMO).
It applies clean with 'patch -l'.
Also attached is a shell script that helps to build a chrooted home dir on
a RedHat 7.2
2001 Feb 22
11
Lets try this push again.. 2.5.1p2 bugs left.
Things that are still outstanding:
1) Solaris/Redhat/HPUX session.c patch. I've not seen a ya or na on
Kevin's pam patch from the Solaris group.
2) Odd Redhat/Debian scp/ssh issues. .. I'm baffled, and I can't
replicate the bug. Nor have I seen anything remotely like it reported.
3) SCO.. Is it happy yet for compiling? =)
Completed:
1) mdoc2man.pl .. Commited into
2001 Feb 27
1
small cleanup patch
configure.in: Open Server 5 doesn't need AC_DEFINE(BROKEN_SAVED_UIDS)
pathnames.h: add #ifndef _PATH_LS to fix
"src/pathnames.h", line 123: warning: macro redefined: _PATH_LS
--
Tim Rice Multitalents (707) 887-1469
tim at multitalents.net
-------------- next part --------------
--- openssh_cvs/configure.in.old Mon Feb 26 18:47:57 2001
+++ openssh_cvs/configure.in Mon Feb 26
2002 Apr 22
0
[Bug 224] New: configure.ac changes for crays
http://bugzilla.mindrot.org/show_bug.cgi?id=224
Summary: configure.ac changes for crays
Product: Portable OpenSSH
Version: 3.1p1
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Build system
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: wendyp
2002 Apr 22
0
[Bug 224] configure.ac changes for crays
http://bugzilla.mindrot.org/show_bug.cgi?id=224
------- Additional Comments From wendyp at cray.com 2002-04-23 09:12 -------
sorry, slight error with that last patch.
try this instead (with 22 april snapshot):
--- configure.ac.orig Mon Apr 22 14:31:27 2002
+++ configure.ac Mon Apr 22 14:32:48 2002
@@ -236,12 +236,29 @@
AC_CHECK_FUNCS(getluid setluid)
MANTYPE=man
2003 Sep 16
6
sshd 3.7p1 dies on MacOSX
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Here's the output from running sshd in debug mode:
debug1: sshd version OpenSSH_3.7p1
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: setgroups() failed:
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
2001 Mar 15
1
News from AIX
Hi,
News from the "AIX is different than the rest of the world" department...
AIX has something similar to setluid() on SCO, just that it uses text
strings (similar to setenv()) and calls it "usrinfo". I've appended
the man page below.
Under normal conditions, well-behaved applications use ttyname(),
logname() and getuid() get the relevant informations, but today
2001 Feb 16
1
OpenSSH 2.3.0p1 port to BSDI BSD/OS
BSD/OS 4.2 comes with OpenSSH 2.1.1p4, patched to support BSDI's
authentication library. However, BSDI's patches have several
problems:
1. They don't run the approval phase, so they can allow users to login
who aren't supposed to be able to.
2. They don't patch configure to automatically detect the BSDI auth
system, so they're not ready to use in a general portable
2003 Oct 26
2
setlogin failed: Function not implemented
I'm using openssh-3.7.1p2 on Linux.
I keep getting setlogin errors in /var/log/messages:
Oct 26 18:44:22 giediprime sshd[7774]: Accepted publickey for root from 127.0.0.1 port 39310 ssh2
Oct 26 18:44:22 giediprime sshd[7776]: error: setlogin failed: Function not implemented
Running LFS 4.0. Happens both on 2.6.0-test8 and 2.4.22-ac1.
When configuring openssh I get this in config.log:
2002 Mar 24
1
FreeBSD 4.x
On FreeBSD 4.x with HAVE_LOGIN_CAP defined the OpenSSH daemon doesn't properly follow standards.
As stated in man 5 login.conf and the process followed by /usr/bin/login,
"The ttys.allow and ttys.deny entries contain a comma-separated list of
tty devices (without the /dev/ prefix) that a user in a class may use to
access the system, and/or a list of ttygroups (See getttyent(3)