Age | Commit message (Collapse) | Author |
|
Also makes the coverage code deterministic
|
|
Makes the codecoverage deterministic (it does not depend on the order of
v4/v6 resolution)
|
|
This adds a hard dependency on one of Botan or gcrypt. Botan is already a
recommended dependency, and gcrypt is probably packaged almost everywhere,
so this should not be a big deal.
ref #3241
|
|
|
|
fix #3235
|
|
|
|
|
|
|
|
fix #2694 (yeah, it was closed, but it was badly fixed)
|
|
|
|
We don’t need any UTF-8 support here, and it’s more portable
|
|
|
|
|
|
If anyone has any reason to believe this is a bad idea, please let me know.
|
|
|
|
|
|
|
|
|
|
Because we “delete all node” and then we use the content of one of these
nodes we got earlier.
|
|
fix #3226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
an internal static object
See https://github.com/randombit/botan/issues/761
|
|
|
|
(which apparently doesn’t work on freebsd)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If available in Botan.
There is an issue where, if botan supports it but we don’t enable it, then
the TLS handshake may fail with some servers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fix #3211
|
|
|
|
This way, TCPSocketHandler only deal with the message sending/receiving, not
the connect() or anything else. This will be used for implementing servers
(because when a client is accepted, we don’t need all the connect() and dns
resolution stuff).
|