See the added comments.  Such bugs are tricky, because the old code
would typically work just fine, only if libuv/OS decided to postpone
copying the data (perhaps large load), we would send two bytes from
this address on C stack - their later value (hard to predict what).

Security risks: the two bytes might theoretically contain information
that was more or less private and we just send it to some DNS server
(possibly over unencrypted TCP), but ATM I find it very unlikely that
this bug could be practically exploited.

clarification to docs for net.bufsize()

See merge request !821

modules/ta_update.test: increase test times for CI

See merge request !822

docs fixes

See merge request !814

- generate most of it from source
- make order the same in implementation and description

CI fixes

See merge request !812

ci: update debian-buster docker image

See merge request !813

Closes #461 and #460.

Tomas Krizek authored 5 years ago and Vladimír Čunát committed 5 years ago

Closes #461

Related #460

Release 4.0.0

See merge request !809

packaging: DoH

See merge request !806

config.ta_update test doesn't play along with others and wants all of
the runner's attention to itself, otherwise it throws a tantrum.

Using 443 as the default port presents too many packaging challenges.
DoH requires configuration to be useful anyway, so users are free to
override this value as they see fit.