> On Nov 18, 2019, at 5:31 AM, Mukund Sivaraman wrote:
>
>> I am initimately familiar with what these fields mean and the code that
>> generates it. The question is not about what the meaning of these fields
>> are.
>>
>> I am asking about where this key format is specified - I want to extend
On Fri, Aug 30, 2019 at 09:56:21AM +0530, Mukund Sivaraman wrote:
> For interoperability, there are other BIND-specific formats to consider
> too such as the journal file format, the control channel protocol,
> etc.
Those seem like separate conversations to me, but I'm happy to have them.
I
Hi Evan
On Thu, Aug 29, 2019 at 04:11:23PM +, Evan Hunt wrote:
> On Thu, Aug 29, 2019 at 07:25:54PM +0530, Mukund Sivaraman wrote:
> > I am asking about where this key format is specified - I want to extend
> > it.
>
> There's never been a written specification as far as I know, and if there
On Thu, Aug 29, 2019 at 07:25:54PM +0530, Mukund Sivaraman wrote:
> I am asking about where this key format is specified - I want to extend
> it.
There's never been a written specification as far as I know, and if there
was one, then it's definitely been obsolete since 2009, because I changed
the
Hi Viktor
On Thu, Aug 29, 2019 at 09:48:31AM -0400, Viktor Dukhovni wrote:
> On Thu, Aug 29, 2019 at 06:25:02PM +0530, Mukund Sivaraman wrote:
> > A tool such as BIND's dnssec-keygen generates the following formatted
> > private keys:
> >
> > [muks@naina ~]$ cat Kexample.org.+008+10638.private
>
On Thu, Aug 29, 2019 at 06:25:02PM +0530, Mukund Sivaraman wrote:
> A tool such as BIND's dnssec-keygen generates the following formatted
> private keys:
>
> [muks@naina ~]$ cat Kexample.org.+008+10638.private
> Private-key-format: v1.3
> Algorithm: 8 (RSASHA256)
> Modulus: [...]
>
A tool such as BIND's dnssec-keygen generates the following formatted
private keys:
[muks@naina ~]$ cat Kexample.org.+008+10638.private
Private-key-format: v1.3
Algorithm: 8 (RSASHA256)
Modulus:
