TLS errors
SwizzinIRC verifies the server’s certificate on every secure connection. If verification fails, the connection is not established and nothing is sent.
| Message | Meaning |
|---|---|
The certificate presented by <host> was rejected (…). The connection was not established and nothing was sent. |
The certificate failed verification. The text in brackets says why, for example that it is expired, issued for a different name, or signed by an unknown authority |
<host> did not present a usable certificate. |
The server sent no certificate SwizzinIRC could use |
<host> rejected the TLS handshake (…). |
The server refused the secure connection. Check the port and the server’s TLS settings |
'<host>' is not a valid server name for certificate checking. |
The host in the profile is not a valid name for certificate checking. Correct it in Edit server |
The TLS handshake with <host> timed out. |
The server did not complete the handshake in time |
On success the server window shows: Secure connection established (<version>); certificate verified for <host>.
Private certificate authorities
Section titled “Private certificate authorities”If a server’s certificate is signed by an authority your computer does not know, give the profile a CA file (a PEM file containing the authority’s certificate). SwizzinIRC then trusts that authority for that profile.
CA file errors:
unusable CA certificate: …: the file is not a valid certificate.the CA file contains no certificates: the file has no certificate in it.
There is no override
Section titled “There is no override”There is no option to ignore certificate errors. This is intentional. Fix the certificate or supply the correct CA file.
An unencrypted connection exists only if you clear Use TLS in the profile or type /server <host> -insecure. It is clearly marked, and passwords are never sent over it.