Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ldns: 1.8.2 update is broken when enabling DNSSEC
Date: Sun, 14 Aug 2022 16:53:56 +0200	[thread overview]
Message-ID: <20220814145356.ZTCSUeia_Ob0o2OSBioJIjhzL4gwulFg6JdHgFrbfnk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38669@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

Closed issue by sbiberhofer on void-packages repository

https://github.com/void-linux/void-packages/issues/38669

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.11_1 x86_64 GenuineIntel uptodate rrFFF

### Package(s) Affected

ldns-1.8.2_1, libldns-1.8.2_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Not yet (at least to my knowledge).

### Expected behaviour

`drill -D` and `ssh` with host key verification over DNS (using SSHFP) to work as usual. :(

### Actual behaviour

Using `drill -D` or `ssh` with `VerifyHostKeyDNS yes` results in an assert failure, regardless of the target domain:

```
% drill -D www.google.com
drill: ./rdata.c:26: ldns_rdf_size: Assertion `rd != NULL' failed.
zsh: IOT instruction  drill -D www.google.com
```


### Steps to reproduce

1. Upgrade to 1.8.2
2. Try to resolve any domain name with `drill -D`, e.g. `drill -D www.google.com`

      parent reply	other threads:[~2022-08-14 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14 12:16 [ISSUE] " sbiberhofer
2022-08-14 12:30 ` paper42
2022-08-14 14:47 ` leahneukirchen
2022-08-14 14:53 ` leahneukirchen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220814145356.ZTCSUeia_Ob0o2OSBioJIjhzL4gwulFg6JdHgFrbfnk@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).