Hi Wytze,
> It looks like the website certificate for wiki.opendnssec.org was renewed
> recently, but the TLSA record still references the old certificate.
Thanks for reporting. I just pushed through new versions of those
records (some other names where affected too). Your plugin will be happy
ag
It looks like the website certificate for wiki.opendnssec.org was renewed
recently, but the TLSA record still references the old certificate.
The Firefox DNSSEC/TLSA Validator plugin is thoroughly unhappy about that.
Regards,
Wytze van der Raay
___
Opend
[Noticed that I didn't send this to the list]
Original Message
Subject: Re: [Opendnssec-user] TLSA
Date: Wed, 05 Dec 2012 08:49:05 +0100
From: Matthijs Mekking
To: Mathieu Arnold
On 12/04/2012 05:05 PM, Mathieu Arnold wrote:
> Hi,
>
> Ok, upgraded ldns, a
Hi,
Ok, upgraded ldns, all is good now.
I get some strange behavior, (v1.3.10), though...
Say, I do :
$ ods-signer sign absolight.net
and in the logs, I get :
Dec 4 17:02:50 ns1 ods-signerd: [scheduler] unable to unschedule task
[read] for zone absolight.net: not scheduled
and :
$ ods-sign
Hi Mathieu,
OpenDNSSEC depends on LDNS for supported RRtypes. You should link
against ldns 1.6.16 if you want to do TLSA.
Best regards,
Matthijs
On 12/04/2012 01:44 PM, Mathieu Arnold wrote:
Hello,
While having lunch, I discovered TLSA records, and I wanted to give it a
spin, but...
Dec
ODS version, LDNS version?
jakob
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
Hello,
While having lunch, I discovered TLSA records, and I wanted to give it a
spin, but...
Dec 4 13:40:53 ns1 ods-signerd: [adapter] error parsing RR at line 17
(Syntax error, could not parse the RR's rdata): _443._tcp.mat.cc.
86400 IN TLSA 3 0 1
D6731A11F7F79A6E38757E0F48589A6887735E33BE2A2E6
