Hi,
On Tue, Oct 13, 2020 at 02:20:15PM +0200, David Vasek wrote:
> Since there was a complaint about this change, we plan to re-enable TCP
> ports reuse in future releases. We also ponder making knotd exit if it
> fails to bind to any of configured TCP ports. We would like hear from
> you whether such a behaviour is what you, users, want best. Please, let
> us know if you prefer this or a different solution.
I'd say "you should never start without all the ports that the config
specified" - so better fail than have a "success!" message with missing
TCP ports that you might only notice some time later.
On the SO_REUSE issue, I do not have strong opinions - if your machine
is comprimised by an attacker that can bind to tcp/53, you're hosed
anyway, so the security argument is not convincing me very much.
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
--
https://lists.nic.cz/mailman/listinfo/knot-dns-users
