Bug 703 - non-interactive commands fail on solaris 8
Summary: non-interactive commands fail on solaris 8
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: PAM support (show other bugs)
Version: 3.7.1p1
Hardware: SPARC Solaris
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
: 728 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-09-23 06:35 AEST by Doke Scott
Modified: 2004-04-14 12:24 AEST (History)
1 user (show)

See Also:


Attachments
patch to fix problem (595 bytes, patch)
2003-09-23 06:37 AEST, Doke Scott
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Doke Scott 2003-09-23 06:35:48 AEST
non-interactive commands fail in PAM tty check on solaris 8.  Not all systems
are affected.  It seems to depend on the system PAM patches.  Problem does not
occur on Solaris 9.
Comment 1 Doke Scott 2003-09-23 06:37:51 AEST
Created attachment 450 [details]
patch to fix problem
Comment 2 Doke Scott 2003-09-23 06:57:10 AEST
Some PAM modules in Solaris 8 require the tty to be set.  So sshd sets it to 
"ssh".  However, some versions of Solaris 8 PAM require the tty to begin with
"/dev/".  Changing auth-pam.c to use "/dev/console", or "/dev/ssh", fixes it.
Comment 3 Darren Tucker 2003-10-07 17:26:57 AEST
I wonder if PAM_TTY=/dev/ssh will break any other platforms?   Maybe it should
be inside an #ifdef PAM_SUN_CODEBASE?

(I don't think using /dev/console is a good idea, though.)
Comment 4 Damien Miller 2003-10-07 20:58:31 AEST
Someone posted this to openssh-unix-dev@

> In case you have problems with 3.7.1p1 on Solaris 8 and have the 
> following messages logged:
> 
> fatal: PAM: pam_open_session(): Can not make/remove entry for 
> session
> 
> Try installing Sun patch 111659-07 or later (or some later patch 
> which incorporates this patch). This fixed it for me, YMMV.

Is this patch installed on the affected system?
Comment 5 Darren Tucker 2003-10-07 22:25:05 AEST
*** Bug 728 has been marked as a duplicate of this bug. ***
Comment 6 Darren Tucker 2004-01-24 18:39:38 AEDT
No reply==closed bug
Comment 7 Damien Miller 2004-04-14 12:24:19 AEST
Mass change of RESOLVED bugs to CLOSED