CC: undisclosed-recipients: ;
MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-2430-1416007201-284.37814-4-0@isc.org>
Content-Disposition: inline
References: <RT-Ticket-37814@isc.org> <546678C0.6040008@redhat.com> <rt-3.8.6-2430-1416007201-284.37814-4-0@isc.org>
Message-ID: <20141114232910.GB70243@isc.org>
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) by bugs.isc.org (Postfix) with ESMTP id 68BEB2D20571 for <bind-suggest@bugs.isc.org>; Fri, 14 Nov 2014 23:29:10 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 4C2A3216C3B; Fri, 14 Nov 2014 23:29:10 +0000 (UTC)
Delivered-To: bind-suggest@bugs.isc.org
User-Agent: Mutt/1.4.2.3i
Subject: Re: [ISC-Bugs #37814] PKCS#11 support for TSIG algorithms
Return-Path: <each@isc.org>
X-Original-To: bind-suggest@bugs.isc.org
Date: Fri, 14 Nov 2014 23:29:10 +0000
To: Francis Dupont via RT <bind-suggest@isc.org>
From: Evan Hunt <each@isc.org>
RT-Message-ID: <rt-3.8.6-2416-1416007750-333.37814-0-0@isc.org>
Content-Length: 280

On Fri, Nov 14, 2014 at 11:20:02PM +0000, Francis Dupont via RT wrote:
> Note I don't yet fully understand your point about
> rndc tsig-list. I am afraid the current only way to
> configure TSIG keys (aka secrets) is to put them
> in the named config file...

There's also TKEY.