From owner-freebsd-questions@FreeBSD.ORG Fri Mar 5 15:46:56 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 503231065686 for ; Fri, 5 Mar 2010 15:46:56 +0000 (UTC) (envelope-from john@starfire.mn.org) Received: from elwood.starfire.mn.org (starfire.skypoint.net [173.8.102.29]) by mx1.freebsd.org (Postfix) with ESMTP id 151D98FC2D for ; Fri, 5 Mar 2010 15:46:55 +0000 (UTC) Received: from elwood.starfire.mn.org (john@localhost [127.0.0.1]) by elwood.starfire.mn.org (8.14.3/8.14.3) with ESMTP id o25Fksts017607; Fri, 5 Mar 2010 09:46:54 -0600 (CST) (envelope-from john@elwood.starfire.mn.org) Received: (from john@localhost) by elwood.starfire.mn.org (8.14.3/8.14.3/Submit) id o25FksFv017606; Fri, 5 Mar 2010 09:46:54 -0600 (CST) (envelope-from john) Date: Fri, 5 Mar 2010 09:46:54 -0600 From: John To: "Randal L. Schwartz" Message-ID: <20100305154654.GB17456@elwood.starfire.mn.org> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <861vfy6add.fsf@blue.stonehenge.com> User-Agent: Mutt/1.4.2.3i Cc: John , freebsd-questions@freebsd.org, Programmer In Training , Anton Subject: Re: Thousands of ssh probes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2010 15:46:56 -0000 On Fri, Mar 05, 2010 at 07:45:02AM -0800, Randal L. Schwartz wrote: > >>>>> "Anton" == Anton writes: > > Anton> But, to allow acces for yourself - you could install wonderfull > Anton> utility = 'knock-knock'. > > Port knocking is false security. > > It's equivalent to adding precisely two bytes (per knock, which can't > be too close or far apart or numerous) to the key length. > > Are you really thinking that increasing your key length from 2048 to 2050 > helps? > > The right solution is proper ssh key management, and intrusion detection, and > if you insist on having password access, use one-time passwords and/or > strength checks. > > If you don't like your logfiles filling up, don't run ssh on port 22. I like > 443, because corporate firewalls tend to pass that... :) Yes - that's exactly what I used to do, and exactly why I used to do it, but now I'm thinking of actually implement https. -- John Lind john@starfire.MN.ORG The inherent vice of capitalism is the unequal sharing of blessings; the inherent virtue of socialism is the equal sharing of miseries. - Winston Churchill