GitLab

For unknown reason, Deckard test might fail with "--- Logging error ---"
from Python interpreter. Experimentally I found out that this does not
happen anymore if kresd is executed with "-f 1", i.e. in non-interactive
mode. I do not know why, but this change seems to hide/solve the problem
and leads to more reliable test suite so it is now enabled by default.

disable module ta_signal_query

See merge request !83

Module is enabled in kresd by default and tests cannot handle it.

deckard: add option --noclean to keep working directory

See merge request !80

Can be used for passing option to Deckard (eg. --noclean).

New option --noclean prevents deleting temp working directory
with passed test. Can be used for debugging.

libfaketime: fix problem with TIMESTAMP_FILE synchronization

See merge request !81

Clearing and writing to TIMESTAMP_FILE is not atomic and libfaketime
can read empty file which represents default behavior and returning
realtime. Create and move new file is atomic and prevent this issue.

kresd now won't put them into answer even in wildcarded cases.
Required for:
https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/371

Kill dns resolver in case of error during daemon set up.

See merge request !76

refs #3

Simple DNSSEC tests

See merge request !36

These tests check whether DNSSEC validator detects data
with invalid signatures.

ci: use git:// protocol for external submodules

See merge request !74

This is workaround for
https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/2148

Given the fact we only read it, and the fact that commit ID is stored
inside our repo, it should not bring any new security problems.

RFC 5011 tests

See merge request !61

Version 3.0 reflects that we dropped support for Python 2.
All the other metadata were updated as well.

(Version 2.y could be the new parser but I forgot to update
the setup.py back then.)

Right now I'm not aware of any reason to invest into Python 2 any further.

Directory rfc5011 contains test generator which can be used to
re-generate the test from scratch. This will get handy when we decide to
generate more RFC 5011 test cases like that.

Per domain trust anchors

Closes #16

See merge request !63

RFC 5011 implementation in kresd and Unbound require separate
trust anchor file for each domain.

Add command needed for kresd to build.

See merge request !72
Related to knot/knot-resolver/!337 and knot/knot-resolver/!355

contrib: update libswrap to avoid problems with CMake 3.9

See merge request !71

There is a trick:
Original answer to query `. NS` contains a lot of NS names which are not
interesting for the test itself. The additional section supplies just
single IP address and the test does not contain root-servers.net. domain
and related infrastructure. This works with current kresd but might
break in future if kresd starts to require all names (or IPv6 or so).

Test not setting AD bit for answer which contains proof of nonexistence of NS…

See merge request !66

resolver: add missing val-override-date to val_unknown_algorithm_insecure test

See merge request !69

The test stopped working because of expired RRSIGs.
This is now fixed by faking system time into middle of validity interval.

update ci dockerfile for WIP branches to pass

See merge request !64

pytest support in CI

See merge request !67

These modules will be required for automated test generation based on
DNS traffic from web browsers.

Test proof of DS non-existence

See merge request !52

kresd: adapt to policy module changes

See merge request !62

MR https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/325
broke some tests because it blocks test. domain by default.

Unblock it in template to allow tests to pass.