| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Wireshark 3.0.5 is able to deal with # comments in middle of log file.
|
| |
|
| |
|
|
|
|
|
| |
It is not used in any way by default, enabling it requires manual
LD_PRELOAD= trickery as described in the source file.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This avoids conflict between GnuTLS's built-in SSLKEYLOG and our hack
for OpenSSL. This would be important for instances which run
DNS-over-TLS using built-in GnuTLS
and at the same time DNS-over-HTTPS using lua-http (based on OpenSSL).
|
|
|
|
|
|
|
|
| |
Original file is GNU GPLv3+ licensed and was copied from
https://git.lekensteyn.nl/peter/wireshark-notes/plain/src/sslkeylog.c
blob: 370668907056f769e2d09bf7bd2e768249049f8f
commit: de25eb75c8d90282ba90396218210c4601603347
Copyright (C) 2014 Peter Wu <peter@lekensteyn.nl>
|
|
|
|
|
| |
Motivation: core-dump might be very useful, and in this case there
are even very useful pointers on the C stack.
|
|
|
|
| |
I didn't plan this well ahead :-/
|
|
|
|
|
| |
We have to use disjoint port ranges for individual test, otherwise
parallel test execution leads to unpredictable results.
|
|
|
|
|
| |
lua-cqueues.socket.fdopen() resets the reuseport flag, so binding Nth
instance without systemd socket activation failed
|
|
|
|
|
| |
The watchdog module now can be loaded without systemd, has customisable
callbacks, and can do real DNS queries and check their results.
|
|
|
|
| |
The integer length didn't match on normal 32-bit linux.
|
|
|
|
|
|
|
|
|
|
|
| |
- home.arpa.: 4. from https://tools.ietf.org/html/rfc8375#section-4
- local.: 4. from https://tools.ietf.org/html/rfc6762#section-22.1
Well, it's just an approximation... if the user specifies a forwarding
policy, any special names will also get forwarded, even though the RFC
says not to. And this code will also reply NXDOMAIN to home.arpa. DS.
Some of these DENY rules are perhaps unnecessary, but for now we keep
the same approach. For arguments see the MR 855 thread and linked ML.
|
| |
|
|
|
|
|
| |
Otherwise plain `modules = { 'prefill' }` will error out,
which is surprising wrt. to style used/allowed by other modules.
|
|
|
|
| |
Fixes: #496
|
|
|
|
|
|
|
|
|
|
| |
This avoids getting into an inconsistent state of the request (assert),
and it also allows some real-life cases to succeed without using
a forbidden address in any way (even though they *are* weird).
I can still imagine weird setups where a request gets failed even
though it would be resolvable without *using* a forbidden address,
but none of these seem reasonable anyway (or common in practice).
|
|
|
|
|
| |
Some people might want the rebinding module generally but still use
policy to allow local addresses in some specific cases.
|
|
|
|
| |
Related #496
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Refusing to answer queries without RD bit makes it harder
to read what data is present in resolver's cache.
|
| |
|
| |
|
|
|
|
| |
Also the log now uses the same format query UID format as elsewhere.
|
|
|
|
|
|
|
|
|
|
| |
State FAIL does not stop iteration because kr_resolve_consume() resets
RESOLVED flag on failed attempts. This causes excessive attempts,
basically forcing kresd to try all authoritative servers before giving
up.
This excessive iteration also caused crash on assert in answer_fail
function.
|
| |
|
|
|
|
|
| |
I don't know any particular case where the bit-test would succeed and
equality wouldn't, but it seems better to take no chances.
|
| |
|
| |
|
| |
|
|
|
|
| |
and slightly better error reporting.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Instead of three days after. This bug was not introduced by the recent
commits moving the code.
|
| |
|
|
|
|
|
|
|
|
| |
ca.crt is cert from root CA
test.crt is cert issued by intermediate CA
chain.crt contains issued cert and intermediate CA cert
issued for: kr.local, 127.0.0.1
|
|
|
|
|
|
|
|
|
|
| |
The cert was updated only once :-/ Now it's updated until the http
module is unloaded.
Also, each socket would create its own ephemeral certificate,
so now that's all shared within the process. Technically we could
synchronise even multiple instances, based on the files, but that would
be much more complex, and it seems an unlikely combination to deploy.
|
|
|
|
|
|
| |
- separate certificate handling into a new file (+ rename the functions)
- handle a list of certs instead of a single one
- minor nitpicks
|
|
|
|
|
| |
Thanks to changes in this branch the functions are called with correctly
typed parameters already, so these weird casts can be deleted.
|