Re: [suPHP] suPHP 0.7.0 released
Added quotes, but not working either: [Sat Dec 27 20:16:21 2008] [error] [client 87.196.147.21] terminate called after throwing an instance of 'suPHP::LookupException' [Sat Dec 27 20:16:21 2008] [error] [client 87.196.147.21] Premature end of script headers: x.phpx -Original Message- From: pmenier [mailto:su...@pmenier.dynalias.net] Sent: sábado, 27 de Dezembro de 2008 9:38 To: Jorge Bastos Cc: 'Sebastian Marsching'; suphp@lists.marsching.biz Subject: Re: [suPHP] suPHP 0.7.0 released Jorge Bastos a écrit : Well it doesn't work for me Sebastian: This is what I get always: [Fri Dec 26 20:58:29 2008] [error] [client 87.196.73.239] terminate called after throwing an instance of 'suPHP::LookupException' [Fri Dec 26 20:58:29 2008] [error] [client 87.196.73.239] Premature end of script headers: x.phpx The virtualhost has: (tested with a new handle to be sure it was being executed) AddType application/x-httpd-phpx .phpx suPHP_AddHandler application/x-httpd-phpx suPHP_Engine On suPHP_UserGroup #5009 #4901 suphp was compiled with: sh configure --with-apxs=/usr/bin/apxs2 --with-min-uid=5000 --with-min-gid=4901 --with-apache-user=www-data --with-logfile=/var/log/suphp/suphp.log CPPFLAGS=-I/usr/include/apr-0 --sysconfdir=/etc/suphp --disable-checkuid --disable-checkgid --with-setid-mode=paranoid --disable-checkpath and this is my suphp.conf (the param --sysconfdir=/etc/suphp will make suphp use /etc/suphp/suphp.conf correct? In /var/log/suphp/suphp.log: [Sat Apr 19 21:07:23 2008] [warn] Script /home/alojamento/albergaria.org/id.phpx resolving to /home/alojamento/albergaria.org/id.phpx not within configured docroot What does this mean? And my suphp.conf is: [global] ;Path to logfile logfile=/var/log/suphp.log ;Loglevel loglevel=warn ;User Apache is running as webserver_user=www-data ;Path all scripts have to be in docroot=/ ;Path to chroot() to before executing script;chroot=/mychroot ; Security options allow_file_group_writeable=false allow_file_others_writeable=false allow_directory_group_writeable=false allow_directory_others_writeable=false ;Check wheter script is within DOCUMENT_ROOT check_vhost_docroot=false ;Send minor error messages to browser errors_to_browser=true ;PATH environment variable env_path=/bin:/usr/bin ;Umask to set, specify in octal notation umask=0077 ; Minimum UID min_uid=100 ; Minimum GID min_gid=100 [handlers] ;Handler for php-scripts ;x-httpd-php=php:/usr/bin/php5-cgi ;php:/usr/bin/php application/x-httpd-phpx=php:/usr/bin/php5 ;Handler for CGI-scripts x-suphp-cgi=execute:!self what can I do? -Original Message- From: Sebastian Marsching [mailto:sebast...@marsching.com] Sent: sexta-feira, 26 de Dezembro de 2008 17:06 To: Jorge Bastos Cc: su...@lists.marsching.com Subject: Re: [suPHP] suPHP 0.7.0 released Jorge Bastos schrieb: 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. I just tested it on my machine and it worked (in paranoid mode). Let's say you wanted to configure suPHP for UID 1234 / GID 4321, then you would use a configuration like this: Directory /home/www/1234 suPHP_Engine On suPHP_UserGroup #1234 #4321 /Directory So instead of specifying user and group name, you just specify user and group numeric id prepended with a #. - Sebastian ___ suPHP mailing list suPHP@lists.marsching.biz http://lists.marsching.com/mailman/listinfo/suphp Hello Documentation of 0.7.0 indicates that you must add quotes in some directives: application/x-httpd-phpx=php:/usr/bin/php5 would be replaced by: application/x-httpd-phpx=php:/usr/bin/php5 and x-suphp-cgi=execute:!self would be replaced by x-suphp-cgi=execute:!self Don't know if it may help but it's probably the basical requirement. Patrick ___ suPHP mailing list suPHP@lists.marsching.biz http://lists.marsching.com/mailman/listinfo/suphp
Re: [suPHP] suPHP 0.7.0 released
Dan Mahoney, System Admin schrieb: ..I sent an email in to the mailing list about this a month ago, stating that is was basically possible since the major blocking issue was that the cgi versions of the php binary didn't do source higlighting (and now apparently do). Got no response from anyone, though. Is this the same thing, or is it done another way? Basically it is the same thing (although it was implemented some month ago). As the PHP binary used for code highlighting is specified separately, you could even use PHP-CLI, if it does not work with PHP-CGI. There was a permissions error that came up during make install -- did that get fixed as well? Yes, it is. I made sure that install-sh has the execute bit set. In fact Autoconf automatically set it. I have no idea, why it was not set in the distribution package of the 0.6.3 release. - Sebastian smime.p7s Description: S/MIME Cryptographic Signature ___ suPHP mailing list suPHP@lists.marsching.biz http://lists.marsching.com/mailman/listinfo/suphp
Re: [suPHP] suPHP 0.7.0 released
Jorge Bastos schrieb: 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. I just tested it on my machine and it worked (in paranoid mode). Let's say you wanted to configure suPHP for UID 1234 / GID 4321, then you would use a configuration like this: Directory /home/www/1234 suPHP_Engine On suPHP_UserGroup #1234 #4321 /Directory So instead of specifying user and group name, you just specify user and group numeric id prepended with a #. - Sebastian smime.p7s Description: S/MIME Cryptographic Signature ___ suPHP mailing list suPHP@lists.marsching.biz http://lists.marsching.com/mailman/listinfo/suphp
Re: [suPHP] suPHP 0.7.0 released
Well it doesn't work for me Sebastian: This is what I get always: [Fri Dec 26 20:58:29 2008] [error] [client 87.196.73.239] terminate called after throwing an instance of 'suPHP::LookupException' [Fri Dec 26 20:58:29 2008] [error] [client 87.196.73.239] Premature end of script headers: x.phpx The virtualhost has: (tested with a new handle to be sure it was being executed) AddType application/x-httpd-phpx .phpx suPHP_AddHandler application/x-httpd-phpx suPHP_Engine On suPHP_UserGroup #5009 #4901 suphp was compiled with: sh configure --with-apxs=/usr/bin/apxs2 --with-min-uid=5000 --with-min-gid=4901 --with-apache-user=www-data --with-logfile=/var/log/suphp/suphp.log CPPFLAGS=-I/usr/include/apr-0 --sysconfdir=/etc/suphp --disable-checkuid --disable-checkgid --with-setid-mode=paranoid --disable-checkpath and this is my suphp.conf (the param --sysconfdir=/etc/suphp will make suphp use /etc/suphp/suphp.conf correct? In /var/log/suphp/suphp.log: [Sat Apr 19 21:07:23 2008] [warn] Script /home/alojamento/albergaria.org/id.phpx resolving to /home/alojamento/albergaria.org/id.phpx not within configured docroot What does this mean? And my suphp.conf is: [global] ;Path to logfile logfile=/var/log/suphp.log ;Loglevel loglevel=warn ;User Apache is running as webserver_user=www-data ;Path all scripts have to be in docroot=/ ;Path to chroot() to before executing script;chroot=/mychroot ; Security options allow_file_group_writeable=false allow_file_others_writeable=false allow_directory_group_writeable=false allow_directory_others_writeable=false ;Check wheter script is within DOCUMENT_ROOT check_vhost_docroot=false ;Send minor error messages to browser errors_to_browser=true ;PATH environment variable env_path=/bin:/usr/bin ;Umask to set, specify in octal notation umask=0077 ; Minimum UID min_uid=100 ; Minimum GID min_gid=100 [handlers] ;Handler for php-scripts ;x-httpd-php=php:/usr/bin/php5-cgi ;php:/usr/bin/php application/x-httpd-phpx=php:/usr/bin/php5 ;Handler for CGI-scripts x-suphp-cgi=execute:!self what can I do? -Original Message- From: Sebastian Marsching [mailto:sebast...@marsching.com] Sent: sexta-feira, 26 de Dezembro de 2008 17:06 To: Jorge Bastos Cc: su...@lists.marsching.com Subject: Re: [suPHP] suPHP 0.7.0 released Jorge Bastos schrieb: 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. I just tested it on my machine and it worked (in paranoid mode). Let's say you wanted to configure suPHP for UID 1234 / GID 4321, then you would use a configuration like this: Directory /home/www/1234 suPHP_Engine On suPHP_UserGroup #1234 #4321 /Directory So instead of specifying user and group name, you just specify user and group numeric id prepended with a #. - Sebastian ___ suPHP mailing list suPHP@lists.marsching.biz http://lists.marsching.com/mailman/listinfo/suphp
