GitLab

This is usefull to make a server asks for a client certificate, but
without failing if the client cannot provide anything.

https://tools.ietf.org/html/rfc5922#section-7.1 says that SubjectAltName should be the only one considered when present, but implementations MAY use CN as well for backward compatibility.
This commit implements the backward compatibility.

Fix mistake in my previous commit. The usage I made of tls_events() was not correct, which resulted in code that could never be executed.

This reverts commit 9ccfe7a4.

Some non-ASCII characters wasn't escaped.

Fix: don't send tls keepalive after an EWOULDBLOCK event. This makes a crash in an assert because the write is never retried.
Furthermore, it makes no sense to send a keepalive if there is data already pending.

Fix TLS setup

See merge request !1

Fix TLS setup - Use both default system certificates and additionally provided CA certifiates chains

Removing the max depth seems to have triggered an issue with an SSL handshake that never terminates, causing flexisip unable to serve clients.

Use TLS certificates from linux's standard path (/etc/ssl/certs), and allow wildcard certificate despite RFC5922.

This fixes some crashes due to the fact that each query has the same resolver

(cherry picked from commit 279f184b)