Date: Tue, 30 Sep 2008 12:00:03 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: freebsd-hackers@FreeBSD.ORG Cc: healey.rich@gmail.com Subject: Re: SSH Brute Force attempts Message-ID: <86abdqkl7g.fsf@ds4.des.no> In-Reply-To: <200809300822.m8U8MMXV026149@lurza.secnetix.de> (Oliver Fromme's message of "Tue, 30 Sep 2008 10:22:22 %2B0200 (CEST)") References: <200809300822.m8U8MMXV026149@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Oliver Fromme <olli@lurza.secnetix.de> writes: > If you're merely annoyed about the large amount of logging entries > caused by the break-in attempts, a good solution is to move the sshd > service from the standard port 22 to a different, non-standard port The best choice is 443, as many corporate firewalls, especially "guest" wifi networks, block all but a few ports (usually 22, 80 and 443, and sometimes 25). There are other, more complicated tricks you can play; for instance, you could set up a web server on the box, and configure it to tunnel SSH using the HTTP Upgrade header; this would require modifications to both ssh (to send the initial HTTP request) and sshd (to take over the connection from the web server). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86abdqkl7g.fsf>