<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Practicing FTP Security</title>
	<atom:link href="http://webhostinggeeks.com/blog/2009/03/17/practicing-ftp-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://webhostinggeeks.com/blog/2009/03/17/practicing-ftp-security/</link>
	<description>Web hosting blog - industry news, trends, products and discussions.</description>
	<lastBuildDate>Fri, 25 Sep 2009 18:30:54 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul beddows</title>
		<link>http://webhostinggeeks.com/blog/2009/03/17/practicing-ftp-security/comment-page-1/#comment-332</link>
		<dc:creator>Paul beddows</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://webhostinggeeks.com/blog/?p=246#comment-332</guid>
		<description>BTW when I posted my comment it inserted  http:// in front of the 2 file names. that should not be there.</description>
		<content:encoded><![CDATA[<p>BTW when I posted my comment it inserted  http:// in front of the 2 file names. that should not be there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul beddows</title>
		<link>http://webhostinggeeks.com/blog/2009/03/17/practicing-ftp-security/comment-page-1/#comment-331</link>
		<dc:creator>Paul beddows</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://webhostinggeeks.com/blog/?p=246#comment-331</guid>
		<description>I was suffering from attacks through FTP, until my web host, ixwebhosting, introduced a simple solution. I upload 2 files to my root called ftp.allow &amp; ft.deny. This allows me to name what IP addresses can have ftp access. Since then I have had no attacks. Its great. All hosts should do this.

If you want to see if it will work on your host which it probably won&#039;t, create these 2 files in this format using any editor and upload them to the root directory:

ftp.deny

ALL: All



ftp.allow

ALL: allowed Ip address
ALL: allowed Ip address</description>
		<content:encoded><![CDATA[<p>I was suffering from attacks through FTP, until my web host, ixwebhosting, introduced a simple solution. I upload 2 files to my root called <a href="http://ftp.allow" rel="nofollow">http://ftp.allow</a> &amp; ft.deny. This allows me to name what IP addresses can have ftp access. Since then I have had no attacks. Its great. All hosts should do this.</p>
<p>If you want to see if it will work on your host which it probably won&#8217;t, create these 2 files in this format using any editor and upload them to the root directory:</p>
<p><a href="http://ftp.deny" rel="nofollow">http://ftp.deny</a></p>
<p>ALL: All</p>
<p><a href="http://ftp.allow" rel="nofollow">http://ftp.allow</a></p>
<p>ALL: allowed Ip address<br />
ALL: allowed Ip address</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Myers</title>
		<link>http://webhostinggeeks.com/blog/2009/03/17/practicing-ftp-security/comment-page-1/#comment-72</link>
		<dc:creator>Scott Myers</dc:creator>
		<pubDate>Tue, 24 Mar 2009 22:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://webhostinggeeks.com/blog/?p=246#comment-72</guid>
		<description>Consider using FTP/WatchDog (www.softwareassist.net) to monitor FTP usage real-time. It makes it easy to keep tabs on FTP server usage (one to many servers); who&#039;s using it, what they are doing with it, transmission of sensitive data, etc.</description>
		<content:encoded><![CDATA[<p>Consider using FTP/WatchDog (www.softwareassist.net) to monitor FTP usage real-time. It makes it easy to keep tabs on FTP server usage (one to many servers); who&#8217;s using it, what they are doing with it, transmission of sensitive data, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
