Skip to content

Commit a45832f

Browse files
committed
Add some documentation on TLS exceptions
1 parent 788d4eb commit a45832f

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/advanced/tls.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,21 @@ which, if you set it in the `Client.Builder`, will blindly allow all connections
2525

2626
For certificate or key pinning, you currently must implement this yourself in your custom
2727
`TrustManager`, though discussions for adding a pinning API are underway.
28+
29+
### TLS Exceptions
30+
31+
If something goes wrong, you may get a `ClientConnectionFailedEvent` with `getCause()`
32+
containing a "SSLEngine problem" and a chain of causes. At the bottom should be the actual
33+
cause of this situation
34+
35+
#### Certificate Expired
36+
37+
The exception may say something like `NotAfter: Mon Jun 10 08:15:43 EDT 2019` which means the
38+
certificate was only valid until that point in time. You should let the admins of that IRC server
39+
know of their mistake. In the mean time, you could work around it by connecting using the
40+
`InsecureTrustManagerFactory`. If writing a client, you could prompt the user to decide if they
41+
want to make this technically risky decision.
42+
43+
#### Self-signed certificate
44+
45+
You could import the certificate! Or, use your own trust manager.

0 commit comments

Comments
 (0)