Libor Peltan authored 8 years ago and Daniel Salzman committed 8 years ago

instead of hard-changing msgID in packet wire, which breaks msgID for the response, we just
set the original msgID when computing the tsig hash to check against

Libor Peltan authored 8 years ago and Daniel Salzman committed 8 years ago

...to display either real Knot running version, numbers of workers, or configure options

Libor Peltan authored 8 years ago and Daniel Salzman committed 8 years ago

Previously, the too-long-check for synthetized cname was only regarding
number of labels, but not overall length.

Maximum TSIG wire size is reached only in empty error response with BADTIME.
In most cases reservation of such a size led to early truncation.