[cobalt-users] Update Available: FP2000 user webs and SSL

[Will DeHaan <will@xxxxxxxxxx>]

A package file exists to correct FrontPage user web access problems on
the RaQ 2 with Red Hat's SecureWeb 3.0 or 3.1 installed.

The update is available at:

 ftp://ftp.cobaltnet.com/pub/experimental/CobaltSSL-RaQ2-3.2-Upgrade.pkg

Instructions, functional details and checksum information are accessible
at:

 ftp://ftp.cobaltnet.com/pub/experimental/CobaltSSL-RaQ2-3.2-Upgrade.txt

Note that the package file is only 645 bytes so don't be alarmed if you
think the ftp transfer failed.

The update does not contain any SecureWeb code which allows it to be
freely distributable.  SecureWeb itself is a commercial package that
should be purchased from Cobalt who has a redistribution deal with Red
Hat.  


	-- Will DeHaan

Jeff Bilicki wrote:
> 
> On RaQ 2 there is problem accessing FrontPage 2000 user sub webs if you
> have Cobalt's SSL add-on installed.   The SSL package contains a suEXEC
> binary that is ready to run.  Apache automatically detects this binary
> and enables it, suEXEC changes the uid and gid on scripts to httpd
> instead uid of the user (see below).   The reason the main web still
> works is because it is supposed to be owned by uid httpd.  To correct
> this problem for the public web server as root type:
> mv /usr/sbin/suexec /usr/sbin/nosuexec
> /etc/rc.d/init.d/httpd.init stop
> /etc/rc.d/init.d/httpd.init start
> 
> Cobalt is working to correct SSL package.
> 
> Jeff Bilicki
> Cobalt Networks
> 
> From: http://www.apache.org/docs-1.2/suexec.html
> After properly installing the suexec wrapper executable, you must kill
> and restart the Apache server. A simple kill -1 `cat httpd.pid` will not
> be enough. Upon startup of the web-server, if Apache finds a properly
> configured suexec wrapper, it will print the following message to the
> console:
> 
> Configuring Apache for use with suexec wrapper.
> 
> If you don't see this message at server startup, the server is most
> likely not finding the wrapper program where it expects it, or the
> executable is not installed setuid root.
> 
> Check your installation and try again.
> 
> One way to use suEXEC is through the User and Group directives in
> VirtualHost definitions. By setting these directives to values different
> from the main server user ID, all requests for CGI resources will be
> executed as the User and Group defined for that <VirtualHost>. If only
> one or neither of these directives are specified for a <VirtualHost>
> then the main server userid is assumed.
> 
> suEXEC can also be used to to execute CGI programs as the user to which
> the request is being directed. This is accomplished by using the ~
> character prefixing the user ID for whom execution is desired. The only
> requirement needed for this feature to work is for CGI execution to be
> enabled for the user and that the script must meet the scrutiny of the
> security checks above.