| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
(u)intptr_t casts seem the best in terms of compliance:
https://stackoverflow.com/q/45220134/587396
Otherwise with clang 18 we can get warnings like
../$path:$line:$col: runtime error: applying non-zero offset $num to null pointer
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../$path:$line:$col
|
| |
|
|\
| |
| |
| |
| | |
This is the last commit in `6.0` before it is shifted into `master`,
with 5.x support being moved to `master-5`.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
Fix cross-references, heading levels, etc.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Mentioning just answers is misleading. Padding is very important
for queries as well; for us that applies during forwarding over TLS.
Also describe /tls/auto_discovery as experimental in the
configuration schema. It's a rather dead experiment from long ago.
I hope it can't be confused with more recent things like
https://datatracker.ietf.org/doc/draft-ietf-dprive-unilateral-probing/
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When inserting rules from a config file, process everything
in a single transaction to avoid using inconsistent sets of rules,
especially in a different instance and/or in case some error happens.
Also fix some over-eager assertions (CHECK_RET).
|
| |/
| |
| |
| | |
We planned it that way for the new config schema - and, why not.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
(and minor other changes)
|
|
|
|
|
| |
Allowing too much seems to have more risk than benefit. For example,
the 2-day TTL on DS records in .com zone (e.g. Slack issue months ago).
|
|
|
|
|
| |
As the web is now, combination without www doesn't redirect https
(only http). So let's switch to the final URL; apex is problematic.
|
|
|
|
|
|
| |
We're the same as knotd in this; it evolved a bit
with libknot and kernel versions. Taken from:
https://www.knot-dns.cz/docs/3.2/singlehtml/#mode-xdp-pre-requisites
|
|
|
|
|
|
| |
https://clangd.llvm.org/design/include-cleaner
Though somehow I'm all the time getting false positives for
"daemon/bindings/impl.h"
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The new limit is over 68 years, so still completely meaningless.
|
|
|
|
|
|
|
|
|
| |
Targeted CIDs: 155456, 155962, 346121, 346123, 346124, 346125,
346126, 346127, 346130, 346131, 346132, 346134, 346135, 346138,
346140, 346145, 346146, 346149, 346152, 346154, 346156, 346157
lib/dnssec/nsec3.c change:
apparently cleaning fallout from my (= vcunat's) commit b5cf61325ae
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The approach of the code was rather hacky, simulating some packets
arriving from upstream and making the module stack CONSUME that.
Instead we take a direct approach now: use the simplified validator API
and then insert into cache directly.
One effect is improved performance, and consequently roughly halving
the lag which happens when prefill module invokes this.
(With root zone the lag goes down to 0.1 s from over 0.2 s,
on my relatively fast CPU. Fortunately it's just once a day.)
|
| |
|
|
|
|
| |
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The purpose of this change is to make it harder to accidentally use the
legacy DoH implementation and free up the "doh" kind which may be used
as an alias to a modern implementation in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To (hopefully) improve readability, rename the typical macro usage of:
if (!kr_assume(x)) y; // to
if (kr_fails_assert(x)) y;
As a convenience, replace the assert without a return value to a more
simple version:
(void)!kr_assume(x); // becomes
kr_assert(x);
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Technically, we return an actual lua table instead of this
pretty-printed representation, but I chose it to be consistent with the
rest of the docs.
|
|
|
|
| |
Details are described in code comments.
|