[Opendnssec-user] How to report a critical issue against OpenDNSSEC?

[Willem Toorop]

I am preparing a release candidate for ldns which will result in an 
updated ldns likely in the last week of November.

With respect to reporting issues, I would prefer using the mailing-list 
for that, but for unknown reasons we did not receive Stephane's initial 
bug report in our inboxes, even though it was received fine by mailman. 
We did receive the follow-up emails though. It would be hard to pinpoint 
what happened, but I'll subscribe with another address (with a different 
email provider) too to reduce the odds for this to happen again.

Op 11-11-2025 om 18:27 schreef Stephane Bortzmeyer via Opendnssec-user:
> On Sat, Nov 08, 2025 at 04:23:27PM +0100,
>   Stephane Bortzmeyer via Opendnssec-user <opendnssec-user at lists.opendnssec.org> wrote
>   a message of 36 lines which said:
>
>> The bug seems to be in the signing software, ldns, I believe. Anyway, ldns clearly has the bug:
> Bug reported (and addressed) in ldns:
>
> https://github.com/NLnetLabs/ldns/issues/285
> _______________________________________________
> Opendnssec-user mailing list
> Opendnssec-user at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xE5F8F8212F77A498_and_old_rev.asc
Type: application/pgp-keys
Size: 7749 bytes
Desc: OpenPGP public key
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20251112/17439d41/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20251112/17439d41/attachment-0001.bin>