Dirk Wetter

Hi Robert! mmm.... first time somebody reported something like this. And I never experience through all the years on a variety of platforms this myself. Looks to me it's somewhat...

Thanks. It's certainly a system thing, but cannot tell why yet. Your system opens for some reason a unix socket to ``/run/dbus/system_bus_socket``, then it tries to send data over it...

Another thing which would be interesting to know whether a self-compiled binary works for you? Sources: https://github.com/drwetter/openssl-1.0.2.bad . Make script: https://github.com/drwetter/testssl.sh/blob/3.0/utils/make-openssl.sh

... and not using -static works?

It seems to me that this is either a bug in ``systemd-resolved`` or a deliberate incompatibility introduced by systemd -- at least in my opinion I do not get why...

.. and what could help to file an issue @ https://github.com/systemd/systemd/issues with the gists provided.

Ok, thanks. The thing with a TLSv1.3-only server seems strange as it should be unrelated to name resolution.

Hi @vdukhovni , thanks for you input! The function above was more a stub thing to signal that some thing is coming. The plan is to check for TLSA records...

1) IDs/classes: sounds like a plan ;-) 2) ``--color``: currently it's expected behavior

@klaernie : Not sure I fully understand you. ``--color`` currently has 4 values. They are fixed. @dcooper16 a while back added a commit (PR #1518) which made the HTML colors...