* Ondřej Surý <ond...@sury.org> [2024-09-04 11:16]:
> First of all, why do you spam i...@isc.org? The ISC pages clearly state how 
> you should report bugs in BIND 9.

First of all, please read your own source before taking a hostile
posture with uncivil tone. I will quote it for you here and give you
the exact URL¹.

> ”BIND 9 Bugs/Feature Requests
>
>  To report a non-security-related bug or request a feature in BIND,
>  please navigate to our GitLab instance and enter your issue
>  there. You will have the option of marking your issue confidential,
>  if necessary. You will need to create an account on GitLab, but you
>  can link your credentials from another GitLab instance or social
>  media account. Once you have logged your issue, you may follow up
>  with us via email to i...@isc.org.”

In particular, be sure to read the last sentence where email is
explicitly solicited for this scenario. The Gitlab instance as a bug
tracker is a non-starter due to a broken CAPTCHA as a barrier to
entry. It is therefore an exclusive website and I am in the excluded
group.

Please also familiarize yourself with Debian policy². Search for
“Don't file bugs upstream” on that page. Note as well the Debian
Social Contract³ which ¶3 states “We will not hide problems”. That
principle implies bug tracker access particularly when upstream
resources are exclusive.

> Second, it’s not clear where the bug is. I would recommend running
> the dig with -d argument and also using strace -f to see where the
> full command gets stuck.

The “-d” parameter is undocumented (another bug) and in this case it
has no effect. No output is generated before the hang. When “strace
-f” is used as follows:

  $ torsocks strace -f dig @"$dns_server" -d -t mx -q "$email_domain" +noclass 
+nocomments +nostats +short +tcp +nosearch

The tail of the output when it hangs is as follows:

===8<----------------------------------------
…
mprotect(0x7efeadb8d000, 4096, PROT_READ) = 0
mprotect(0x7efeae19a000, 4096, PROT_READ) = 0
mprotect(0x56499f748000, 4096, PROT_READ) = 0
mprotect(0x7efeae1ce000, 8192, PROT_READ) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, 
rlim_max=RLIM64_INFINITY}) = 0
munmap(0x7efeae16c000, 101230)          = 0
readlink("/etc/malloc.conf", 0x7ffdd2b44370, 4096) = -1 ENOENT (No such file or 
directory)
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7efeae184000
madvise(0x7efeae184000, 4096, MADV_DONTNEED) = 0
munmap(0x7efeae184000, 4096)            = 0
getuid()                                = 1000
geteuid()                               = 1000
futex(0x7efeadf547c0, FUTEX_WAIT_PRIVATE, 2, NULL
===8<----------------------------------------

Footnotes:

¹ https://www.isc.org/reportbug/
² https://www.debian.org/Bugs/Reporting
³ https://www.debian.org/social_contract

Reply via email to