Bug 260 - "Memory Fault" in Solaris 6 and Solaris 7
"Memory Fault" in Solaris 6 and Solaris 7
Status: RESOLVED FIXED
Product: Sudo
Classification: Unclassified
Component: Sudo
1.6.9
Sun Solaris 2.x
: normal normal
Assigned To: Todd C. Miller
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-12 18:00 MDT by Marnix A. van Ammers
Modified: 2007-09-13 19:15 MDT (History)
0 users

See Also:


Attachments
Patch to work around a pam bug in Solaris (647 bytes, patch)
2007-09-13 19:15 MDT, Todd C. Miller
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Marnix A. van Ammers 2007-09-12 18:00:33 MDT
I created Solaris packages for Solaris 6 through Solaris 10 using sudo 1.6.9p5 .  I found that the "sudo" produced in Solaris 6 and Solaris 7 would say "Memory Fault" and die.  On the Solaris 6 machine I compiled with gcc version 3.2.2 .  On the Solaris 7 machine I compiled with gcc version 2.8.1 .  In both cases I used the following configuration options:

 --prefix=/var/tmp/PGEsudo
 --sysconfdir=/usr/local/etc
 --with-editor=/usr/pge2/bin/vim:/usr/bin/vi
 --disable-root-sudo
 --with-timeout=600
 --enable-noargs-shell
 --disable-shared
 --enable-static
 --with-logfac=auth
  --with-loglen=160
  --with-ignore-dot
  --mandir=${prefix}/man
  --with-insults
  --with-all-insults
  --with-pc-insults

I pulled an older version 1.6.8p12 and that version compiles and works OK in both Solaris 6 and Solaris 7.  Just thought you might want to know.

Marnix A.  van Ammers
Comment 1 Todd C. Miller 2007-09-13 10:11:43 MDT
This appears to be a PAM-related issue.  If you run configure with the --without-pam option it will use regular password authentication like 1.6.8p12 does.
Comment 2 Todd C. Miller 2007-09-13 19:15:05 MDT
Created attachment 213 [details]
Patch to work around a pam bug in Solaris

Fixes a segv on Solaris 7 and earlier.
Comment 3 Todd C. Miller 2007-09-13 19:15:30 MDT
There is a bug in one of the Solaris pam modules where they use the value of the PAM_RHOST variable without first checking to see if it has been set.  I've attached a patch to workaround the issue.  The patch will be present in the next sudo release.