Date: Fri, 05 Mar 2010 07:51:52 -0800 From: merlyn@stonehenge.com (Randal L. Schwartz) To: John <john@starfire.mn.org> Cc: freebsd-questions@freebsd.org, Programmer In Training <pit@joseph-a-nagy-jr.us>, Anton <anton@sng.by> Subject: Re: Thousands of ssh probes Message-ID: <86sk8e4vhj.fsf@blue.stonehenge.com> In-Reply-To: <20100305154654.GB17456@elwood.starfire.mn.org> (john@starfire.mn.org's message of "Fri, 5 Mar 2010 09:46:54 -0600") References: <20100305125446.GA14774@elwood.starfire.mn.org> <4B910139.1080908@joseph-a-nagy-jr.us> <20100305132604.GC14774@elwood.starfire.mn.org> <1108389354.20100305154152@sng.by> <861vfy6add.fsf@blue.stonehenge.com> <20100305154654.GB17456@elwood.starfire.mn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "John" == John <john@starfire.mn.org> writes: John> Yes - that's exactly what I used to do, and exactly why I used to do John> it, but now I'm thinking of actually implement https. Rent more than one IP. :) I have a block of 8 for exactly that reason. It allows me to run sshd on 443 *and* https on a different 443, and a mailer on one 25 and a high-mx mail spamtrap on another port 25. stonehenge.com mail is handled by 5 blue.stonehenge.com. stonehenge.com mail is handled by 666 spamtrap.stonehenge.com. The spamtrap is a shiny object for spam, and anything that goes there gets blocked for an hour from hitting the low port. I presented this at a conference once. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>; Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86sk8e4vhj.fsf>