<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Web Hosting Support</title>
	<atom:link href="http://www.hostanswers.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hostanswers.net</link>
	<description>Linux Apache cPanel WHM Fantastico PHP MySQL Hosting</description>
	<pubDate>Thu, 16 Apr 2009 16:07:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
	<language>en</language>
			<item>
		<title>Selinux file_contexts: Multiple same specifications for /usr/local/lost\+found.</title>
		<link>http://www.hostanswers.net/linux-hosting/selinux-file_contexts-multiple-same-specifications-for-usrlocallostfound/</link>
		<comments>http://www.hostanswers.net/linux-hosting/selinux-file_contexts-multiple-same-specifications-for-usrlocallostfound/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 16:07:49 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
		
		<category><![CDATA[Linux Hosting]]></category>

		<guid isPermaLink="false">http://www.hostanswers.net/?p=161</guid>
		<description><![CDATA[If you receive the message &#8220;/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /usr/local/lost\+found.&#8221; in your email, this usually means the system thinks you have a user account home directory in /usr/local and this user is allowed to ssh to your server.
If there is a system account, make sure you change the shell to /sbin/nologin or /bin/false. In [...]]]></description>
			<content:encoded><![CDATA[<p>If you receive the message &#8220;<strong>/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /usr/local/lost\+found.</strong>&#8221; in your email, this usually means the system thinks you have a user account home directory in /usr/local and this user is allowed to ssh to your server.</p>
<p>If there is a system account, make sure you change the shell to <strong>/sbin/nologin </strong>or<strong> /bin/false.</strong> In order for the changes to take effect, run</p>
<p><strong>semodule -B</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.hostanswers.net/linux-hosting/selinux-file_contexts-multiple-same-specifications-for-usrlocallostfound/feed/</wfw:commentRss>
		</item>
		<item>
		<title>PHP Fatal error:  Allowed memory size of xxxxx bytes exhausted</title>
		<link>http://www.hostanswers.net/linux-hosting/php-fatal-error-allowed-memory-size-of-xxxxx-bytes-exhausted/</link>
		<comments>http://www.hostanswers.net/linux-hosting/php-fatal-error-allowed-memory-size-of-xxxxx-bytes-exhausted/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 14:06:49 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
		
		<category><![CDATA[Linux Hosting]]></category>

		<guid isPermaLink="false">http://www.hostanswers.net/?p=150</guid>
		<description><![CDATA[You may see the error message &#8220;PHP Fatal error:  Allowed memory size of xxxxx bytes exhausted (tried to allocate xxxxxxx bytes) in Unknown on line 0&#8243; while accessing some php pages which indicates that those php files requires more memory for it to execute than the one specified in php.ini file. If the memory_limit value [...]]]></description>
			<content:encoded><![CDATA[<p>You may see the error message &#8220;<strong>PHP Fatal error:  Allowed memory size of xxxxx bytes exhausted</strong> (tried to allocate xxxxxxx bytes) in Unknown on line 0&#8243; while accessing some php pages which indicates that those php files requires more memory for it to execute than the one specified in php.ini file. If the memory_limit value is manipulated in server side <strong>php.ini</strong> file, it will be applied to all the php files server side.</p>
<p>In order to overcome the error without modifying the server side php.ini file, you need to use the <strong>ini_set function</strong> to increase the memory limit inserting the following code in the php file itself. Keep on increasing the memory limit unless the error disappears.</p>
<p><strong>ini_set(&#8221;memory_limit&#8221;,&#8221;64M&#8221;);</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.hostanswers.net/linux-hosting/php-fatal-error-allowed-memory-size-of-xxxxx-bytes-exhausted/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HowTo: Mod_Security Installation on Linux/Plesk server</title>
		<link>http://www.hostanswers.net/linux-plesk/howto-mod_security2-installation-on-linuxplesk-server/</link>
		<comments>http://www.hostanswers.net/linux-plesk/howto-mod_security2-installation-on-linuxplesk-server/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 21:37:55 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
		
		<category><![CDATA[Linux Plesk]]></category>

		<category><![CDATA[mod security configuration and rules]]></category>

		<category><![CDATA[modsecurity audit_logs]]></category>

		<category><![CDATA[modsecutiry modules]]></category>

		<category><![CDATA[Mod_Security2 Installation on Linux]]></category>

		<category><![CDATA[Mod_Security2 Installation on Plesk]]></category>

		<category><![CDATA[what is APXS]]></category>

		<guid isPermaLink="false">http://www.hostanswers.net/?p=126</guid>
		<description><![CDATA[The following is a step by step guide on &#8220;How to install Mod_security2 on a Linux/Plesk server&#8221; which is use to secure your server from Apache exploits.
First download and extract mod_security
cd /etc/httpd/
wget http://www.modsecurity.org/download/modsecurity-apache_2.5.7.tar.gz
tar -zxf modsecurity-apache_2.5.7.tar.gz
cd modsecurity-apache_2.5.7/apache2
Next compile mod_security at a module using apxs. BTW, APXS is an Apache tool for building Apache modules.
apxs -cia mod_security2.c
you [...]]]></description>
			<content:encoded><![CDATA[<p>The following is a step by step guide on &#8220;<strong>How to install Mod_security2 on a Linux/Plesk server</strong>&#8221; which is use to secure your server from Apache exploits.</p>
<p>First download and extract mod_security<br />
<strong>cd /etc/httpd/<br />
wget http://www.modsecurity.org/download/modsecurity-apache_2.5.7.tar.gz<br />
tar -zxf modsecurity-apache_2.5.7.tar.gz<br />
cd modsecurity-apache_2.5.7/apache2</strong></p>
<p>Next compile mod_security at a module using <strong>apxs</strong>. BTW, APXS is an Apache tool for building Apache modules.<br />
<strong>apxs -cia mod_security2.c</strong></p>
<p>you may realise you don&#8217;t have the apxs on your server, in that case you will have to install <strong>httpd-devel</strong> package using yum.<br />
<strong>yum install httpd-devel</strong></p>
<p>Once mod_security2 is installed, make sure you have the &#8216;<strong>LoadModule</strong>&#8216; line in your Apache configuration (httpd.conf) file and the module &#8220;<strong>mod_security2.so</strong>&#8221; itself under &#8216;modules&#8217; directory.</p>
<p><strong>LoadModule security2_module modules/mod_security2.so</strong></p>
<p>Now, create a modsecurity configuration file as modsecurity.conf under /etc/httpd/conf.d/ directory, as *.conf in the conf.d directory gets loaded. Below is the sample configuration file you may use:</p>
<blockquote><p>#SecFilterEngine DynamicOnly<br />
SecFilterEngine On<br />
SecFilterDefaultAction &#8220;deny,log,status:500&#8243;<br />
SecFilterScanPOST On<br />
SecFilterCheckURLEncoding On<br />
SecFilterCheckCookieFormat On<br />
SecFilterCheckUnicodeEncoding Off<br />
SecFilterNormalizeCookies On<br />
SecFilterCookieFormat 1<br />
SecServerResponseToken Off</p>
<p>#If you want to scan the output, uncomment these<br />
#SecFilterScanOutput On<br />
#SecFilterOutputMimeTypes &#8220;(null) text/html text/plain&#8221;</p>
<p># Only record the interesting stuff<br />
SecAuditEngine RelevantOnly<br />
SecAuditLog /var/log/modsecurity/audit_log</p>
<p># You normally won&#8217;t need debug logging<br />
SecFilterDebugLevel 0<br />
SecFilterDebugLog /var/log/modsecurity/modsec_debug_log</p>
<p>#Include the sample rule files, you just downloaded<br />
Include /etc/httpd/conf.d/apache2-rules.conf*<br />
Include /etc/httpd/conf.d/badips.conf*<br />
Include /etc/httpd/conf.d/blacklist.conf*<br />
Include /etc/httpd/conf.d/blacklist2.conf*<br />
Include /etc/httpd/conf.d/proxy.conf*<br />
Include /etc/httpd/conf.d/rootkits.conf*<br />
Include /etc/httpd/conf.d/rules.conf*</p></blockquote>
<p>Download the sample rules from<br />
<strong>wget http://hostanswers.net/modsecurity/sample_mod_rules.tar.gz</strong></p>
<p><strong>Please note</strong>: These are just the default rules that come with Mod_security2 and you need to modify them as per your needs.</p>
<p>At the end, make sure you create a modsecurity directory and &#8216;audit_log&#8217; file and restart apache.<br />
<strong>mkdir /var/log/modsecurity<br />
touch /var/log/modsecurity/audit_log<br />
service httpd restart</strong></p>
<p>If you have problems accessing websites look at error log at<br />
<strong>/etc/httpd/logs/audit_log</strong></p>
<p>Just FYI, if you wish <strong>to disable mod_security</strong>, just <strong>comment the modsecurity &#8216;LoadModule&#8217; line</strong> in your Apache configuration file and restart apache.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hostanswers.net/linux-plesk/howto-mod_security2-installation-on-linuxplesk-server/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
