Bug 468 - 3.5p1 authentication error on Solaris 8
Summary: 3.5p1 authentication error on Solaris 8
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: -current
Hardware: UltraSPARC Solaris
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-15 07:02 AEDT by Christopher L. Barnard
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher L. Barnard 2003-01-15 07:02:07 AEDT 
OpenSSH 3.5p1 conflicts with the Solaris 8 cron patch 109007-08.  Installing -08
generates the authenication error when doing a cron command:

ld.so.1: crontab: fatal: relocation error: file crontab: symbol
audit_crontab_not_allowed: referenced symbol not found
Killed

The Sun engineer I spoke with believes that this is an authentication/auditing
mismatch between OpenSsh and Sun.  Backing the patch down to rev -07 fixes the
issue temporarily.
Comment 1 William Knox 2003-01-15 07:36:23 AEDT 
I'm not seeing this behavior on my Solaris 8 systems - latest patch cluster
(1/8/03), including patch 109007-08.
Comment 2 Christopher L. Barnard 2003-01-15 07:58:44 AEDT 
On both a SS5 andd a V880. both running Solaris 8, with patch 109007-07, crontab
-l is just fine.  With patch 109007-08, crontab -l returns

ld.so.1: crontab: fatal: relocation error: file crontab: symbol
audit_crontab_not_allowed: referenced symbol not found
Killed

What version of SSH are you running?  What platform are you running?  I only
have the sun engineer's word that this is even related to ssh...
Comment 3 William Knox 2003-01-15 08:07:57 AEDT 
Multiple platforms (all sun4u, including a V880) and OpenSSH 3.5p1
Comment 4 Damien Miller 2003-01-15 10:18:29 AEDT 
How is OpenSSH involved here? Do you get the error when logging in from the console?

This looks like a shared library issue which has nothing to do with OpenSSH.
Comment 5 Christopher L. Barnard 2003-01-17 03:48:18 AEDT 
I agree, I do not think this is a problem with OpenSsh.  I think it is a problem
with Sun's patch 109007-08.  I have installed and removed this patch on a system
that did not have any ssh at all installed to prove that it is unrelated.  I am
continuing to work with Sun.  Thank you for your time.
Comment 6 Damien Miller 2004-04-14 12:24:18 AEST 
Mass change of RESOLVED bugs to CLOSED