Displaying 20 results from an estimated 6000 matches similar to: "[Bug 802] sshd of openssh-3.8p1 doesn't link on Tru64."
2002 Aug 11
4
OSF/1 or Tru64 patch for Privsep
Either this never made it to the list or no one cares about Tru64. This
is the last time I'll send this patch to the list. If no one steps up and
finishes it or provides me with enough information to fix any remaining
bugs (one being complaint that 'ssh site cmd' does not work right).
If there is no activity on this for a week. I'll post it to bugzilla and
will ignore any
2004 Mar 27
1
Problems Compiling sshd - OpenSSH 3.8p1 on Tru64 UNIX V4.0F PK#7 (OSF)
I am trying to compile sshd 3.8p1 on Tru64 UNIX V4.0F Patch Level 7.
Previously I've compiled the entire 3.6.1p2 distribution with no problems.
The problem seems to occur when linking sshd. The linker is unable to find
xcrypt and shadow_pw functions (openbsd-compat/*.c). The libopenbsd-compat
seems to have built without errors. I configure as follows:
CC=cc CFLAGS=-O LDFLAGS=-non_shared
2004 Sep 20
3
[Bug 933] compile problem on tru64 5.1A code outside of a #ifdef that should not be included on tru64
http://bugzilla.mindrot.org/show_bug.cgi?id=933
Summary: compile problem on tru64 5.1A code outside of a #ifdef
that should not be included on tru64
Product: Portable OpenSSH
Version: 3.8p1
Platform: Alpha
OS/Version: OSF/1
Status: NEW
Severity: normal
Priority: P2
Component: Build
2004 Mar 19
1
[Bug 814] Turning on OSF SIA causes linker errors in sshd
http://bugzilla.mindrot.org/show_bug.cgi?id=814
Summary: Turning on OSF SIA causes linker errors in sshd
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: OSF/1
Status: NEW
Severity: critical
Priority: P1
Component: Build system
AssignedTo: openssh-bugs at mindrot.org
2000 Nov 17
8
To Do list...
This is just portable todo list. From the sounds of it Markus has his own
to do list. But can everyone review and let me know if there is anything
missing from this list. (Note.. I'm not looking for 'SSH should support
XYZ feature.' unless it's directly related to portability.) Or if there
is anything on this list that has been completed. (Namely Tru64 SIA
support?)
Thanks.
2004 Mar 04
3
[Bug 807] Compilation failure--> ld: Unresolved: xcrypt shadow_pw
http://bugzilla.mindrot.org/show_bug.cgi?id=807
Summary: Compilation failure--> ld: Unresolved: xcrypt shadow_pw
Product: Portable OpenSSH
Version: 3.8p1
Platform: Alpha
OS/Version: OSF/1
Status: NEW
Severity: major
Priority: P2
Component: Build system
AssignedTo: openssh-bugs at mindrot.org
2002 Sep 04
2
uid transition and post-auth privsep (WAS Re: possible fundamental problem with tru64 patch) (fwd)
What do we loose by not having post-auth privsep?
What code is executed between authorization and actual setting of the
effective uid?
On Tue, 3 Sep 2002, Chris Adams wrote:
> Once upon a time, Toni L. Harbaugh-Blackford <harbaugh at nciaxp.ncifcrf.gov> said:
> > It appears that the integration of the sia session setup will either
> > have to be rethought or abandoned
2001 Mar 20
1
Tru64 UNIX SIA in 2.5.2p1 is hosed
Something really hosed Digital/Tru64 UNIX SIA support in 2.5.2p1. I
haven't been able to figure out what changed in the code, but the
symptom seems to be that the TTY name being registered with SIA is
truncated to eight characters. This apparently prevents it from
matching with entries in the tty database, and the dreaded "Cannot
obtain database information on this terminal
2003 Sep 25
4
[Bug 716] OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64 UNIX)
http://bugzilla.mindrot.org/show_bug.cgi?id=716
Summary: OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64
UNIX)
Product: Portable OpenSSH
Version: -current
Platform: Alpha
OS/Version: OSF/1
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo: openssh-bugs
2000 Oct 15
1
Patch for Digital Unix SIA authentication
A while back, I sent in a patch that added Digital Unix SIA
authentication to OpenSSH. Well, I just figured out that it didn't
handle everything correctly (locked accounts could still log in). I
thought I had checked that, but I guess I missed it.
Anyway, here is a patch against OpenSSH 2.2.0p1 that fixes this.
--
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator
2003 May 12
2
[Bug 296] Priv separation does not work on OSF/1
http://bugzilla.mindrot.org/show_bug.cgi?id=296
------- Additional Comments From dtucker at zip.com.au 2003-05-12 18:42 -------
Can this bug be closed? The ChangeLog seems to indicate that it's been
addressed.
20030320
[snip]
- (bal) Disable Privsep for Tru64 after pre-authentication due to issues
with SIA. Also, clean up of tru64 support patch by Chris Adams
<cmadams at
2001 Mar 21
1
Tru64 UNIX SIA in 2.5.2p1 is hosed (still)
The recent patch posted by Steve VanDevender <stevev at darkwing.uoregon.edu>
for fixing the session code on Tru64 isn't quite right -- it still fails
in the case of NO tty being allocated.
The problem is that s->tty is a char[TTYSZ] rather than a char *, and
hence can't hold a NULL. Calling sia_ses_init() with the tty being an
empty string doesn't signify no tty, and
2001 Feb 21
2
SCO 5.0.5 setluid patch
I downloaded openssh-2.5.1p1 as soon as it was on the ftp servers just
to get the setluid patch. After compiling and installing on 5.0.5 I saw
that the luid still wasn't being set correctly whether sshd was run from
inetd or as a daemon from /etc/rc2.d/. I fiddled around and moved the
setluid() stuff up higher in session.c and now luid is now being set
correctly. I provided a regular diff
2001 May 01
1
Problem with .hushlogin in Tru64 UNIX 4.0e
I have tried this with openssh-2.5.2p2 and openssh-SNAP-20010501.
I have noticed that with a .hushlogin file in my home directory I still
get messages.
With the .hushlogin file I get these messages:
Last successful login for ricardo: Tue May 1 08:06:00 2001 from
blah.mnsu.edu
Last unsuccessful login for ricardo: Tue May 1 08:05:21 2001 from
blah.mnsu.edu
Without the .hushlogin file I get
2002 Aug 14
1
[Bug 353] login failure on tru64
http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=353
------- Additional Comments From Wayne.Corelli at hp.com 2002-08-14 23:56 -------
A temporary work around is to set "UsePrivilegeSeparation no" in sshd_config
althought this disables all the "enhanced security" features.
Would someone PLease address this!!!
------- You are receiving this mail
2004 Apr 14
1
[Bug 802] sshd configured with SIA doesn't link on Tru64.
http://bugzilla.mindrot.org/show_bug.cgi?id=802
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |821
nThis| |
Summary|sshd of openssh-3.8p1 |sshd configured with SIA
2001 Feb 12
2
OSF_SIA bug in 2.3.0p1
Is anyone maintaining the OSF_SIA support in openssh? This seems to be an
obvious bug triggered if you try to connect as a non-existant user.
>From auth1.c line 459
#elif defined(HAVE_OSF_SIA)
(sia_validate_user(NULL, saved_argc, saved_argv,
get_canonical_hostname(), pw->pw_name, NULL, 0,
NULL, "") == SIASUCCESS)) {
#else /*
2002 Aug 15
1
[Bug 296] Priv separation does not work on OSF/1
http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=296
mouring at eviladmin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |weberc at grc.nia.nih.gov
------- Additional Comments From mouring at eviladmin.org 2002-08-16 07:24 -------
2003 Sep 16
1
OpenSSH 3.7p1, PrivSep, and Tru64 broken (sorry)
Well, I had just finally gotten around to downloading a snapshot to test
the latest on Tru64 a couple of days ago but hadn't had a chance to
build it yet, and 3.7p1 has now been released. Sigh.
The problem is that Tru64 setreuid() and setregid() are broken, so
privsep doesn't work.
This could also be a security problem for SIA authentication in general
(any version of OpenSSH on Tru64,
2003 Sep 24
1
Patches for compatibility with Heimdal's libsia_krb5 SIA module
I have found the following patches to be desirable for using sshd on a
Tru64 UNIX system with the Kerberos 5 SIA module (libsia_krb5.so) from
Heimdal.
These patches do the following:
1) preserve context between the password authentication and the session
setup phases. This is necessary because the Heimdal SIA module stores
Kerberos context information as mechanism-specific data in