At 16:20 02.09.2000 -0400, Peter Green wrote:
>Okay. You didn't followup on my previous point, but that may mean that it
>doesn't work on your platform. :) ``Does it work to simply setuid the
>qmailadmin cgi, wherever it is actually located, and forego the explicit
>suEXEC User/Group statements?''
That't one of the starting point problems. Using suEXEC you cannot run any
SUID/SGID programs anymore.
>> The "qmailadmin" binary is in located in
>> /home/vpopmail/public_html/qmailadmin/cgi-bin/qmailadmin
>> and is called via
>> https://server/~vpopmail/qmailadmin/cgi-bin/qmailadmin
>
>Then I think you want cgipath to be ``/qmailadmin/cgi-bin/qmailadmin''.
Not really, in my scenario it should be
"/~vpopmail/qmailadmin/cgi-bin/qmailadmin"
And here I made a review and found, what's working:
--enable-cgipath='/~vpopmail/qmailadmin/cgi-bin/qmailadmin'
I've tried this before sometimes, but without the ticks (') around :-(
Now my scenario is working!
Thanks for helping,
Peter
BTW: But the hint for the developers: Looks like the generation mechanism
of URLs for Links and Buttons is different.
BTW2 (perhaps in interest for others): The (in previous e-mails described)
scenario is useful in following case (in my opinion):
* You want use "qmailadmin" and "sqwebmail" over SSL
* You have a host with more than one IP address and some IP-based (not
virtual) SSL hostings
* You want to allow scripting on that SSL hosts, but want to disable
cross-side-effects between them [script of server 1 are able looks in the
data of server 2..., can be happen if running as apache-user...] (therefore
you must specify "user" and "group" at this hosts and use suEXEC)
* You want enable "qmailadmin" and "sqwebmail" on such hosts
