Skip to content

Ignore $HOME/.digrc (3.0)#1949

Merged
drwetter merged 3 commits into3.0from
digrc_3.0
Aug 1, 2021
Merged

Ignore $HOME/.digrc (3.0)#1949
drwetter merged 3 commits into3.0from
digrc_3.0

Conversation

@drwetter
Copy link
Copy Markdown
Collaborator

@drwetter drwetter commented Jul 31, 2021

Newer dig versions have an option to ignore $HOME/.digrc, older don't.

This commit adds a patch checking for the availability of
such an option and uses it by default. See #1894.

If this option doesn't exist then still dig is used and can still lead to
wrong output. Unfortunately Debian-based distros are not very
good at this. Debian 10, Ubuntu 18.04 still use dig 9.11, whereas
Opensuse 15.2 has 9.16.

Debian 11 and Ubuntu 20.04 use that too.

For the stable 3.0-branch: dig has been moved down in the row
of resolver functions to mitigate a bug / minimize the likelihood that
$HOME/.digrc is being used.

Newer dig versions have an option to ignore $HOME/.digrc, older
don't.

This commit adds a patch checking for the availability of
such an option and uses it by default.

If doesn't exist then still dig is used and can still lead to
wrong output. Unfortunately Debian-based distros are not very
good at this. Debian 10, Ubuntu 18.04 still use dig 9.11, whereas
Opensuse 15.2 has 9.16.

Debian 11 and Ubuntu 20.04 use that too.

Thus to be considered for the stable 3.0-branch: move
dig in the resolver functions a couple of lines down.
@drwetter drwetter changed the title Ignore $HOME/.digrc Ignore $HOME/.digrc (3.0) Jul 31, 2021
drwetter added 2 commits July 31, 2021 15:22
... because there's a higher possibility for the stable branch
that people use $HOME/.digrc
@drwetter drwetter merged commit 91523be into 3.0 Aug 1, 2021
@drwetter drwetter deleted the digrc_3.0 branch August 1, 2021 19:00
drwetter added a commit that referenced this pull request Sep 1, 2021
Similar to #1972.

* the ignore ~/.digrc option from dig is now parsed from the builtin help
* there was a potential DNS call which is now avoided
* the +noidnout check is now parsed from the builtin help
* the OPENSSL_CONF="" in check_resolver_bins() was moved a few lines higher to avoid other errors in the terminal
* redo check for noidnout by also using the help function of dig

See also #1949
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant