Hi Sebastian, Does this new version allows the broken functionality of using numeric userid's and groupid's to work? I never had success on configuring suPHP because if this, no system users on my machine.
Jorge, > -----Original Message----- > From: suphp-boun...@lists.marsching.biz [mailto:suphp- > boun...@lists.marsching.biz] On Behalf Of Sebastian Marsching > Sent: quinta-feira, 25 de Dezembro de 2008 17:14 > To: su...@lists.marsching.com > Subject: [suPHP] suPHP 0.7.0 released > > Hi, > > as a christmas present for the suPHP community, I just released suPHP > 0.7.0. After this version has been running on one of my production > servers for more than half a year, I regard it as stable enough to > release it to the public. > > This release brings some features that have been on the wish list for a > very long time: > > - Source code highlighting: You can now use the new content type > "application/x-httpd-php-source" to render the highlighted source code > of PHP files instead of executing them as scripts. This function > basically works like the highlighting function of mod_php. The only > thing, you have to do, is to use the "suPHP_PHPPath" directive to set > the path to the PHP executable used for syntax highlighting. As the > syntax highlighting is performed with webserver privileges, you have to > make the file readable by the webserver. This should prevent accidental > disclosure of confidential data (e.g. database passwords). > > - Multiple docroots: You can now specify more than one docroot that may > contain PHP scripts. For example you can specify > /var/www:${HOME}/public_html to allow scripts in /var/www or the > public_html directory within a user's home directory. > > - Variables in configuration values: You can now use several variables > in the docroot and chroot configuration values. This is especially > useful in combination with the new support for mod_userdir: You can now > use suPHP with userdirs by setting a docroot of $HOME/public_html (or > any other path you have configured for mod_userdir). When using suPHP's > paranoid mode, you do not have to specify the user for each directory > explicitly: mod_suphp will automatically use the user name supplied by > mod_userdir. > > - suPHP_AddHandler and suPHP_RemoveHandler on per vhost level: Now you > do not have to use a <Directory> container for suPHP_AddHandler and > suPHP_RemoveHandler. You can just use them on global or per vhost level > as well. However, per directory settings will override per server > settings. > > There are some minor improvements too: > > - The AddType directive now works with Apache 1.3, too. Therefore you > can use AddType instead of AddHandler if you do not want the special > way > Apache handles multiple file extensions when using AddHandler. > > - No "underquoted definition" warning when rebuilding the GNU Autoconf > scripts. While this had absolutely no consequences it was a nasty > warning message that is gone now. > > The is a VERY IMPORTANT NOTICE you have to consider when you want to > UPGRADE to suPHP 0.7.0. > > Existing configuration files (suphp.conf) WILL NOT WORK with suPHP > 0.7.0: For the multiple docroot feature the colon (:) is now a special > characters that separates multiple values for the same configuration > directive. Therefore you have to escape the colon within a single value > using the backslash or around the whole value. > > For example instead of > > x-httpd-php=php:/usr/bin/php-cgi > > you know have to use either > > x-httpd-php="php:/usr/bin/php-cgi" > > or > > x-httpd-php=php\:/usr/bin/php-cgi > > Be sure to change this in your existing configuration files when > upgrading to the new version. > > > Have fun with the new release and happy holidays to everyone. > > > - Sebastian > > _______________________________________________ > suPHP mailing list > suPHP@lists.marsching.biz > http://lists.marsching.com/mailman/listinfo/suphp _______________________________________________ suPHP mailing list suPHP@lists.marsching.biz http://lists.marsching.com/mailman/listinfo/suphp
