Matteo Corti

> Sorry, this goes a little bit above my head. 😄 > > As far as I understand https://datatracker.ietf.org/doc/html/rfc5280#section-5.2.7 multiple certificates are possible and can be used to validate the...

We send a ```CONNECT``` control packet as client ```a``` ``` \x10\x0d\x00\x04MQTT\x04\x00\x00\x00\x00\x01a ``` but we don't close.

I am not an expert: if someone has an example of the payload to close cleanly, please post it.

Not really a bug but a missing feature. On failure, not all the data is available, and the formatting could be complicated. I'll have a look.

I would rather try to keep one option and just display what is available.

I'm still struggling with the failure format, as the content could be very different depending on the error. From one single sentence as for a wrong command line option, to...

Not yet, if I find the time I'll try to implement a solution

It could be caused by the check if the port is actually open. Can you please post the output with the ```--debug-time``` command line option?

I just installed bookworm and something is very strange: a standard check on github.com takes more than 32 seconds. On all the other Linux systems (Fedora, Debian) it takes less...

Something to do with ```/bin/timeout```: Example ``` corti@debian check_ssl_cert> time /bin/curl --silent --user-agent 'check_ssl_cert/2.70.0' --location \"http://cacerts.digicert.com/DigiCertGlobalRootCA.crt\" real 0m0.010s user 0m0.009s sys 0m0.001s corti@debian check_ssl_cert> time /bin/timeout 105 /bin/sh -c "/bin/curl...