<?xml version='1.0' encoding='utf-8'?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0"><updated>2007-09-22T17:13:00Z</updated><id>tag:blog.limedaley.com,2018:/isso/thread/post/using-tcpd-wrappers-with-pure-ftpd</id><title>Comments for blog.limedaley.com/post/using-tcpd-wrappers-with-pure-ftpd</title><entry><id>tag:blog.limedaley.com,2018:/isso/582/2535</id><title>Comment #2535</title><updated>2007-09-22T17:13:00Z</updated><author><name>Jon Daley</name></author><link href="https://blog.limedaley.com/post/using-tcpd-wrappers-with-pure-ftpd#isso-2535" /><content type="html">&lt;p&gt;I have to do regular FTP, because it is harder for most people to figure out how to do scp or sftp.  I never use ftp myself, but most of my customers do.  I suppose that Microsoft may have done the security world a favor by breaking FTP in the latest version of Internet Explorer - people will get used to using other clients, and then sftp or scp are about the same, from the non-technical user's viewpoint.&lt;/p&gt;
&lt;p&gt;The return value for them is the same whether they get a wrong password or wrong username.  The trouble is that hackers have basically unlimited resources (by hacking into unprotected machines all over the world (probably mostly in the US) and then using those hacked machines as a large network of coordinated attack machines).&lt;/p&gt;
&lt;p&gt;When I said they occasionally get good usernames, that means out of all of their random guessing (and sometimes not so random - like &amp;quot;salemsattic&amp;quot;, or &amp;quot;limedaley&amp;quot;, etc.) sometimes they get real usernames, and then I have to count on the strength of my customers' passwords.  If the hacker has a wrong username, I don't really care how many times he tries to login, as long as the CPU load stays low.&lt;/p&gt;
&lt;p&gt;Denyhosts is great because it only allows so many attempts before blocking the IP.  I no longer have to even think about ssh hack attempts, because the hacker has about 15-30 seconds at most to guess a username and valid password.  If he guesses wrong usernames (or worse, privileged usernames (that wouldn't have ssh access anyway, so it is kind of silly to guess those), he only has one attempt before his ip is blocked forever (and broadcast to a blacklist, so he will be blocked before he even tries anything on other people's machines).&lt;/p&gt;
&lt;p&gt;I'll try sending you an email, but I thought you didn't accept non-secured email, and I am not sure if I have the floppy with your key on it...  :)&lt;/p&gt;</content></entry><entry><id>tag:blog.limedaley.com,2018:/isso/582/2534</id><title>Comment #2534</title><updated>2007-09-22T15:33:30Z</updated><author><name>mdrew</name></author><link href="https://blog.limedaley.com/post/using-tcpd-wrappers-with-pure-ftpd#isso-2534" /><content type="html">&lt;p&gt;I think the bigger problem here is that there is apparently a way for hackers to guess something and determine from your server's behavior useful information like 'valid username'.  I don't understand why it fails differently depending on whether a correct username is entered (assuming a bad password).&lt;/p&gt;
&lt;p&gt;P.S. send me an email so I can contact you.&lt;/p&gt;</content></entry><entry><id>tag:blog.limedaley.com,2018:/isso/582/2533</id><title>Comment #2533</title><updated>2007-09-22T15:14:22Z</updated><author><name>mdrew</name></author><link href="https://blog.limedaley.com/post/using-tcpd-wrappers-with-pure-ftpd#isso-2533" /><content type="html">&lt;p&gt;Are you trying to server *really* big files?  Why not scp or sftp?&lt;/p&gt;</content></entry><entry><id>tag:blog.limedaley.com,2018:/isso/582/2532</id><title>Comment #2532</title><updated>2007-09-19T20:34:05Z</updated><author><name>jondaley</name></author><link href="https://blog.limedaley.com/post/using-tcpd-wrappers-with-pure-ftpd#isso-2532" /><content type="html">&lt;p&gt;For documentation purposes, my first attempts at the regular expressions were:&lt;/p&gt;
&lt;p&gt;SSHD_FORMAT_REGEX=.* (sshd.*:|\[sshd\]|pure-ftpd:) (?P.*)&lt;/p&gt;
&lt;p&gt;USERDEF_FAILED_ENTRY_REGEX=(?@(?P.*)) \[WARNING\] Authentication failed for user \[(?P.*)\]&lt;/p&gt;</content></entry></feed>