When specifying a wrong CA, no useful error messages are generated

[m4z <[email protected]…>]

This is basically the same underlying (user) problem as #1104 describes, just with a different cause, hence the separate ticket.

I switched from the default setup where certificate == ca in bcfg2.conf on the server to one where they where separate files and stupid me changed only the certificate line, and forgot all about the ca line. My problem then was that even with debug mode enabled on both the server and client (on the same machine),

• the server did not log anything about a connection attempt at all, and
• the client only logged "Failed to download probes:".

I had to confirm with tcpdump that the connection was even attempted.

Please add useful SSL debug messages, and keep up the good work. (: