From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LQTA0-0006EQ-2n for garchives@archives.gentoo.org; Fri, 23 Jan 2009 21:01:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E53B7E070E; Fri, 23 Jan 2009 21:01:50 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.148]) by pigeon.gentoo.org (Postfix) with ESMTP id A0E3BE070E for ; Fri, 23 Jan 2009 21:01:50 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 4so652980eyg.10 for ; Fri, 23 Jan 2009 13:01:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=iUFD81nZLb7TJP29h3ZZ2rPUf+leZwGe0aVYfuH2hwk=; b=e2ttbqUxTQ0CpEKYYuXIN8oIUwz80J6YcMpcKHVS1LYMqUtvMWiVy88M4CoazTo+WL GDdNUQdBNCyjjLiOgL/9N+oUNdtJtha3NeZD5I3VMHEKBlwtYucluDlAUkYyDNw8entC bIgAjkkLvo8xzs3DJVlw7Tyn5PaWUE2Hwm2kY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=PeWBkYXtQvbl2IDzKBHEFAvs0VqhE4sZeYt7moV/vcNpTTghAirS72CEsArST+jqHC QvsDeRUs3tYdhIoOw7vsz5+H/KLPuCxifNRLQSOpO8nttfzAysTZNmNK0lnbDKx3Qa/h TWTf4I+p9JZbR0Q40UTPEOGuCwAowdZ41BCz4= Received: by 10.210.57.5 with SMTP id f5mr6686811eba.14.1232744509950; Fri, 23 Jan 2009 13:01:49 -0800 (PST) Received: from ?172.20.0.4? ([196.210.139.153]) by mx.google.com with ESMTPS id 10sm5423943eyd.56.2009.01.23.13.01.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 23 Jan 2009 13:01:49 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Why isn't sshd blocking repeated failed login attempts? Date: Fri, 23 Jan 2009 23:00:37 +0200 User-Agent: KMail/1.9.10 References: <200901232233.21122.alan.mckinnon@gmail.com> <58965d8a0901231254s7788b435ke487378b35327652@mail.gmail.com> In-Reply-To: <58965d8a0901231254s7788b435ke487378b35327652@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901232300.38035.alan.mckinnon@gmail.com> X-Archives-Salt: a4654744-5ce7-43b9-aa81-9a478a2e6fab X-Archives-Hash: 1115f50c6e49f7b8065d171c5bfe4577 On Friday 23 January 2009 22:54:24 Paul Hartman wrote: > > A friend once mentioned on a forum that he'd managed to set up static > > libwrap rules in hosts.allow|deny for addresses that don't change and > > additionally port-knocking for himself to open up port 22 for a few > > minutes. I don't recall how he did this, only that he claimed to have > > done it. > > I've never tried it but I have always liked the idea. I connect to > sshd from linux (my laptop), windows (my work desktop) and symbian (my > phone). > > knockd and the knocking client should be no problem for linux & > windows, but for my phone I'd probably have to make one myself. Is it > as simple as making a connection to a specific sequence of ports with > specific timing? I could probably do that easily in python. Sounds > like a project for this weekend. :) I'm no expert but AFAIK that is the general idea -- alan dot mckinnon at gmail dot com