Re: [Acme] Issue: Allow ports other than 443
Peter Eckersley <pde@eff.org> Thu, 26 November 2015 02:03 UTC
Return-Path: <pde@mail2.eff.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D64D1A872E for <acme@ietfa.amsl.com>; Wed, 25 Nov 2015 18:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.587
X-Spam-Level:
X-Spam-Status: No, score=-7.587 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HWcDbD4uDfEp for <acme@ietfa.amsl.com>; Wed, 25 Nov 2015 18:03:29 -0800 (PST)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D58671A87A9 for <acme@ietf.org>; Wed, 25 Nov 2015 18:03:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=VJIo70hO9LFurmFKgDSp4+QMUPXFmgsiRe56XLT8lFY=; b=5MD4QLvYiU/pD1/NG2jvMeafA9h/s9+2SYuZ7XIy8n67uOT3PX9FPLhKQNlksZdqhOyB+lXCLgpD7x2TK5zlxxXiHQHtwb9H+Z1MEDPUYV7lJfnjezunSoOtzJnikhXg7iv1BLzJTt2NHg3oamucXEQ7lRqRVW2thgUx6CHjPtQ=;
Received: ; Wed, 25 Nov 2015 18:03:28 -0800
Date: Wed, 25 Nov 2015 18:03:28 -0800
From: Peter Eckersley <pde@eff.org>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Message-ID: <20151126020328.GU18430@eff.org>
References: <5e9b22a3942d4a39981878b13e4a7752@usma1ex-dag1mb1.msg.corp.akamai.com> <0630035C-E4F6-41AA-A339-7101B448F0FA@vigilsec.com> <CABkgnnUxSwMmOR=QVE-gMvj9dHW6Tk2Z=EO7RDx6E5zVAp_SrQ@mail.gmail.com> <20151124033325.GH18430@eff.org> <56545B4C.3020406@cisco.com> <m2io4ro83g.wl%randy@psg.com> <CAHbuEH4Yh-UUin1F0ajsRAHrzrEZ+eDraXd9xLxcnY5kQVxPUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHbuEH4Yh-UUin1F0ajsRAHrzrEZ+eDraXd9xLxcnY5kQVxPUg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/cuoAEMnN0ILr9wsl91vCXsC3ECA>
Cc: Randy Bush <randy@psg.com>, Martin Thomson <martin.thomson@gmail.com>, IETF ACME <acme@ietf.org>, Russ Housley <housley@vigilsec.com>, Eliot Lear <lear@cisco.com>
Subject: Re: [Acme] Issue: Allow ports other than 443
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Nov 2015 02:03:32 -0000
The argument for a scan is not that it will be comprehensive. There's a huge amount of software out there that has started using various ports in standard and non-standard ways; the more software happens to use a given port, the more risk of remote attacks on ACME DV via quirks or bugs in that software. So it would be best do a scan to pick a port that is comparatively unused in the wild. On Tue, Nov 24, 2015 at 11:37:36AM -0500, Kathleen Moriarty wrote: > I agree with Eliot, I don't think a scan is needed to make a decision > here. Having managed several networks that would not have allowed you > access from some random scanner, I don't think you'll get all the data > you are looking for. In a well managed network, the IDS/IPS should > detect that it is a scan and block all future probes once you hit a > small number of ports/IPs. So you may get a small sample with > everything else failing within an address block. Granted, not all > networks are managed well and you may get a good amount of data. > > If this connection was expected to a few servers, then a network > manager might just allow those only on the assigned port. > > Without any hat on, I agree that a port + 443 as an alternate is a good plan. > > Kathleen > > On Tue, Nov 24, 2015 at 8:11 AM, Randy Bush <randy@psg.com> wrote: > >> Isn't this precisely what .well-known was meant to address? > > > > fun small research project. what percentage of well-known ports can > > you connect to from the outside to a machine inside cisco? hell, to > > what percentage of well-known ports outside cisco can you reach from > > inside? > > > > well-known does not correlate well with open to access by IT security > > departments. > > > > randy > > > > _______________________________________________ > > Acme mailing list > > Acme@ietf.org > > https://www.ietf.org/mailman/listinfo/acme > > > > -- > > Best regards, > Kathleen > -- Peter Eckersley pde@eff.org Chief Computer Scientist Tel +1 415 436 9333 x131 Electronic Frontier Foundation Fax +1 415 436 9993
- [Acme] Issue: Allow ports other than 443 Salz, Rich
- Re: [Acme] Issue: Allow ports other than 443 Russ Housley
- Re: [Acme] Issue: Allow ports other than 443 Martin Thomson
- Re: [Acme] Issue: Allow ports other than 443 Douglas Calvert
- Re: [Acme] Issue: Allow ports other than 443 Martin Thomson
- Re: [Acme] Issue: Allow ports other than 443 Randy Bush
- Re: [Acme] Issue: Allow ports other than 443 Peter Eckersley
- Re: [Acme] Issue: Allow ports other than 443 Martin Thomson
- Re: [Acme] Issue: Allow ports other than 443 Randy Bush
- Re: [Acme] Issue: Allow ports other than 443 Hugo Landau
- Re: [Acme] Issue: Allow ports other than 443 Eliot Lear
- Re: [Acme] Issue: Allow ports other than 443 Randy Bush
- Re: [Acme] Issue: Allow ports other than 443 Kathleen Moriarty
- Re: [Acme] Issue: Allow ports other than 443 Yoav Nir
- Re: [Acme] Issue: Allow ports other than 443 Eliot Lear
- Re: [Acme] Issue: Allow ports other than 443 Niklas Keller
- Re: [Acme] Issue: Allow ports other than 443 Eliot Lear
- Re: [Acme] Issue: Allow ports other than 443 Niklas Keller
- Re: [Acme] Issue: Allow ports other than 443 Martin Thomson
- Re: [Acme] Issue: Allow ports other than 443 Peter Eckersley
- Re: [Acme] Issue: Allow ports other than 443 Phillip Hallam-Baker
- Re: [Acme] Issue: Allow ports other than 443 Eliot Lear
- Re: [Acme] Issue: Allow ports other than 443 Stephen Farrell
- Re: [Acme] Issue: Allow ports other than 443 Yoav Nir
- Re: [Acme] Issue: Allow ports other than 443 Stephen Farrell
- Re: [Acme] Issue: Allow ports other than 443 Rob Stradling
- Re: [Acme] Issue: Allow ports other than 443 Yoav Nir
- Re: [Acme] Issue: Allow ports other than 443 Darren J Moffat
- Re: [Acme] Issue: Allow ports other than 443 Eliot Lear