From each@isc.org Thu Jun 8 18:27:34 2017 CC: MIME-Version: 1.0 In-Reply-To: Content-Disposition: inline X-RT-Interface: API References: Message-ID: <20170608182734.GA73603@isc.org> content-type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) by bugs.isc.org (Postfix) with ESMTP id 5D6F971B5A8 for ; Thu, 8 Jun 2017 18:27:34 +0000 (UTC) Received: by bikeshed.isc.org (Postfix, from userid 10292) id 54454216C1E; Thu, 8 Jun 2017 18:27:34 +0000 (UTC) Delivered-To: bind9-review@bugs.isc.org Subject: Re: [ISC-Bugs #45183] [PATCH] Alternative NSEC3 mode for nsec3hash User-Agent: Mutt/1.5.23 (2014-03-12) Return-Path: X-Original-To: bind9-review@bugs.isc.org Date: Thu, 8 Jun 2017 18:27:34 +0000 To: "Tony Finch via RT" From: "Evan Hunt" RT-Message-ID: Content-Length: 710 On Thu, Jun 08, 2017 at 04:15:41PM +0000, Tony Finch via RT wrote: > Aww, the reason for that was to make it easy to copy and paste in the > terminal, without having to configure a shell alias, e.g. You can still copy and paste the bit after the NSEC3. If it makes it easier to find the place you wanted to cut and paste, then I guess we could add an optional first argument that's skipped if it contains NSEC3 or NSEC3PARAM. I don't like the idea of using argv[0] for this, though. Incidentally, for a point-zero release in the future, I wonder if we should make the -r the default for nsec3hash and add a different option for backward compatibility. The existing argument ordering makes no sense at all.