<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Netvouz / falko / tag / suphp</title>
<link>http://netvouz.com/falko/tag/suphp?feed=rss</link>
<description>falko&#39;s bookmarks tagged &quot;suphp&quot; on Netvouz</description>
<item><title>How To Set Up suPHP On A Debian Etch Based ISPConfig Server | HowtoForge</title>
<link>http://www.howtoforge.com/suphp_debian_etch_ispconfig</link>
<description>This tutorial shows how to install and use suPHP with the ISPConfig control panel on a Debian Etch server. When you have set up suPHP on your ISPConfig server, you are able to run the PHP scripts under the admin user of the website instead of the Apache user.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Mon, 23 Apr 2007 09:20:50 GMT</pubDate>
</item><item><title>PHP-FPM/Nginx Security In Shared Hosting Environments (Debian/Ubuntu)</title>
<link>http://www.howtoforge.com/php-fpm-nginx-security-in-shared-hosting-environments-debian-ubuntu</link>
<description>If you want to use nginx and PHP-FPM for shared hosting environments, you should make up your mind about security. In Apache/PHP environments, you can use suExec and/or suPHP to make PHP execute under individual user accounts instead of a system user like www-data. There&#39;s no such thing for PHP-FPM, but fortunately PHP-FPM allows us to set up a &quot;pool&quot; for each web site that makes PHP scripts execute as the user/group defined in that pool. This gives you all the benefits of suPHP, and in addition to that you don&#39;t have any FTP or SCP transfer problems because PHP scripts don&#39;t need to be owned by a specific user/group to be executed as the user/group defined in the pool.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Sun, 25 Sep 2011 16:51:02 GMT</pubDate>
</item></channel></rss>