| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
When positive wildcard expansion happens, NSEC(3) records are needed
to prove that the expansion was allowed. If the NSEC3 had too many
iterations, we downgrade the answer to insecure status, but
unintentionally we also dropped the NSEC3 record from the answer.
That was breaking DNSSEC validation of that answer, e.g. when
forwarding to Knot Resolver. The validator needs the NSEC3 -
either to validate the expansion or to determine that it's too expensive.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Just as read-only aggregates of the split v4+v6 pairs.
|
| |
| |
| |
| |
| |
| | |
Let's have .total4 and .total6, too. Then .total could be expressed
as a sum of *three* (including .internal), so it's still counted
separately, as an exception.
|
|/
|
|
| |
(cherry picked from commit 44df5dd0d0fedfae390e7137572bcb14270e4d48)
|
|\
| |
| |
| |
| | |
Coverity fixes
See merge request knot/knot-resolver!1543
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This check was introduced to fix Clang-Tidy errors, but was factually
not completely correct, tripping Coverity Scan.
|
|/
|
|
|
| |
This should appease Coverity Scan, and make the garbage collector
consistent with the rest of the Resolver.
|
|
|
|
|
| |
The detections are mostly academic and useless for our purposes. We have
other static analyzers that better suit our needs.
|
|\
| |
| |
| |
| | |
CI/CD overhaul
See merge request knot/knot-resolver!1533
|
| |
| |
| |
| |
| |
| |
| | |
It used to just throw BrokenPipeError, but newer versions of Python have
a separate exception for when the connection is closed in violation of
TLS rules, which Knot Resolver does deliberately so as to not waste time
on properly closing TLS connections with misbehaving peers.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Knot Resolver disables resumption on TLS <=1.2 as it is vulnerable to
replay attacks, so the test makes no sense, as that one was specifically
disabled for TLS >=1.3 (Python had no support for it at the time).
We should make a new test for this with TLS 1.3 support.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit makes lots of changes to the C code to appease the
Clang-Tidy linter. Some of the less obvious ones are due to C's weird
semantics regarding handling of numeric literals.
We also disable a bunch of the detections because they are
super-pedantic, arguably useless, or we have our own unwritten coding
style rules that solve the issues.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the bulk of the CI/CD overhaul.
Most of the changes are to the `.gitlab-ci.yml` file, where the build
images used are replaced with the ones provided by the
`knot-resolver-ci` repository. Some cleanups have also been done.
The commit also adds unit testing with Knot Resolver built against
multiple versions of Knot DNS, including the `master` branch. The
`master` branch image is built nightly in the `knot-resolver-ci` repo.
We have also removed `scan-build`, as its tests change frequently, with
lots of false-positives, which are very different on each version, and
there is no good way to ignore some detections. Clang-Tidy covers some
of the same issues, and we also have Coverity Scan. Should be more than
enough.
A few config tests were also excluded in the AddressSanitizer tests,
because they produce false-positives.
|
|/
|
|
|
|
| |
- Do `go mod tidy` before running the test, even in CI
- Add `go.sum` to `.gitignore`
- Compatibility with Go 1.15 (Debian 11)
|
|\ |
|
|/
|
|
|
| |
Unfortunately the `latest` tag is amd64 only right now,
even though it did have both recently. I hope this will work reliably.
|
|\ |
|
| |
| |
| |
| |
| | |
knot_wire_next_label used to return NULL when applied to . (root)
but that's not allowed anymore, and some of our calls relied on that.
|
|/
|
|
| |
knot_wire_next_label isn't allowed with NULL wire anymore.
|
|\
| |
| |
| |
| | |
Fix macOS GitHub actions
See merge request knot/knot-resolver!1537
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
gitlab-ci: push docs to the website (manual CI)
See merge request knot/knot-resolver!1530
|
|/ |
|
|\
| |
| |
| |
| | |
nits: unused variable, improved #include path
See merge request knot/knot-resolver!1529
|
| |
| |
| |
| |
| | |
The issue was exposed when working on rrl-wip branch:
lib/dnssec/nsec.c:19:10: fatal error: resolve.h: No such file or director
|
|/
|
|
| |
Reported by clang.
|
|\
| |
| |
| |
| | |
daemon/meson.build: add install_rpath to kresd
See merge request knot/knot-resolver!1528
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This fixes the default use-case for developers when they put their
install prefix somewhere where the system `LD_LIBRARY_PATH` does not
point. Before this, `kresd` would fail to start after `ninja install`
because it would not be able to find the `libkres.so` library.
The original workaround to this was to use `meson configure
-Ddefault_library=static`, but firstly, we would like it to be working
with the default settings, and secondly, we would like to have it as
similar to what most users will encounter as possible.
|
|\
| |
| |
| |
| | |
Release 5.7.2
See merge request knot/knot-resolver!1522
|
| | |
|
| |
| |
| |
| |
| | |
Fixes the script for users who have `log.showSignature` set to `true` in
their git config.
|
|/ |
|
|\
| |
| |
| |
| | |
daemon/lua: fix on 32-bit systems with 64-bit time_t
See merge request knot/knot-resolver!1510
|
|/
|
|
|
|
| |
This improves the heuristics.
The problem would be detected by meson, but not when cross-compiling,
in which case things would mostly run OK, except some lua code/modules.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
This is so that it is more obvious that the PyPI package actually has
the `python-` prefix.
|
|/ |
|
|\
| |
| |
| |
| | |
improve assertions around current releases
See merge request knot/knot-resolver!1506
|
| |
| |
| |
| |
| |
| |
| | |
Ideally we would've done that at once with increasing NSEC3 strictness,
i.e. in 5.7.1 + 6.0.6, as otherwise we could run into some recoverable
assertions until the records got removed or expired.
We at least do the bump now.
|
|/
|
|
| |
It was no longer correct after commit cc5051b444130 (KeyTrap).
|
| |
|
|\
| |
| |
| |
| | |
DNSSEC verification complexity could be exploited to exhaust CPU resources and stall DNS resolvers.
Solution boils down mainly to limiting crypto-validations per packet.
|
| |
| |
| |
| | |
in a separate commit, as it will tend to conflict if patching
|