Implement changing client-side TLS certificate and key paths, and reloading certificate/key at runtime when doing a REHASH (BLABOUNCER command or SIGHUP).

1 files changed, 5 insertions, 2 deletions

diff --git a/README b/README
index 7381b49..5b217cf 100644
--- a/README
+++ b/README
@@ -23,7 +23,8 @@ If you don't specify one using "-c /path/to/configuration/file" then the example
 for you at $HOME/.blabouncer/blabouncer.conf when starting for the first time.
 
 Certain configuration options can be changed at runtime by changing them in the configuration file, then
-issuing a BLABOUNCER REHASH command, or by sending SIGHUP to the blabouncer process.
+issuing a BLABOUNCER REHASH command, or by sending SIGHUP to the blabouncer process.  This will also
+reload the client-side TLS certificate and key if clienttls = "1".
 
 These options can be changed by issuing a BLABOUNCER REHASH command or by sending SIGHUP to blabouncer:
  - nicks
@@ -34,6 +35,8 @@ These options can be changed by issuing a BLABOUNCER REHASH command or by sendin
  - logging
  - replaylogging
  - debug
+ - certfile
+ - keyfile
 
 == Commands ==
 
@@ -41,7 +44,7 @@ Once connected to blabouncer with an IRC client, you can use the following speci
 
 "BLABOUNCER REPLAY [[[days:]hours:]minutes]" (To replay a given length of time of replay log.)
 "BLABOUNCER QUIT [quit message]" (To quit blabouncer, optionally sending [quit message] to the server.)
-"BLABOUNCER REHASH" (To reload settings from the configuration file, see above for details.)
+"BLABOUNCER REHASH" (To reload configuration file settings and the client-side TLS certificate/key - see above for details.)
 "BLABOUNCER CLIENTCODE [clientcode]" (To set an identifier for the current client for auto replaying just
 what this client has missed.)
 "BLABOUNCER LISTCLIENTS" (To list all connected clients and their authentication status.)