On Thu, Feb 12, 2009, Birger Krägelin wrote:
> I just did an update of my apache installation. Now apache-suphp gives an
> error.
>
> old version was "apache-suphp-0.6.2-20080101.sparc64-solaris10"
> current version is " apache-suphp-0.7.0-20081225.sparc64-solaris10"
>
> I didn't change my configuration, and I didn't change my "build" script.
>
> I have
> -Dapache-suphp::with_suphp_ugid_mode=owner \
> -Dapache-suphp::with_suphp_ugid_check=no
>
> But now suphp throws an exception
>
> terminate called after throwing an instance of 'suPHP::LookupException'
> Premature end of script headers: index.suphp
>
> LookupException gets thrown, when owner of suphp script isn't in /etc/passwd,
> but 'ugid_check=no' should disable this check.
>
> Any suggestions?
I checked suPHP 0.7.0: the Autoconf options which we used under
apache-suphp::with_suphp_ugid_check=no for 0.6.0 are still documented
in the doc/INSTALL but are not longer implemented. And even the code
seems to be no longer have any conditionals for ignoring those lookup
failures. I guess the author of suPHP completely removed this whole
functionality because it has looked not reasonable to him. So, sorry,
suPHP 0.7.0 no longer seems to contain this functionality.
PS: I'm just curious: why can your users not looked up? Aren't they
in the system password database or at least NIS?
Ralf S. Engelschall
[email protected]
www.engelschall.com
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List [email protected]
