summary refs log tree commit diff
path: root/synapse
diff options
context:
space:
mode:
authorMatthew Hodgson <matthew@matrix.org>2017-10-24 18:49:44 +0100
committerMatthew Hodgson <matthew@matrix.org>2017-10-24 18:49:49 +0100
commitefd0f5a3c58b62344c6981c4076eb23873ad57e3 (patch)
tree55fd73c95d8e0d6321e5734379d9b2a8a49d9543 /synapse
parentMerge pull request #2567 from matrix-org/erikj/group_fed_update_profile (diff)
downloadsynapse-efd0f5a3c58b62344c6981c4076eb23873ad57e3.tar.xz
tip for generating tls_fingerprints
Diffstat (limited to '')
-rw-r--r--synapse/config/tls.py6
1 files changed, 6 insertions, 0 deletions
diff --git a/synapse/config/tls.py b/synapse/config/tls.py
index 247f18f454..4748f71c2f 100644
--- a/synapse/config/tls.py
+++ b/synapse/config/tls.py
@@ -109,6 +109,12 @@ class TlsConfig(Config):
         # key. It may be necessary to publish the fingerprints of a new
         # certificate and wait until the "valid_until_ts" of the previous key
         # responses have passed before deploying it.
+        #
+        # You can calculate a fingerprint from a given TLS listener via:
+        # openssl s_client -connect $host:$port < /dev/null 2> /dev/null |
+        #   openssl x509 -outform DER | openssl sha256 -binary | base64 | tr -d '='
+        # or by checking matrix.org/federationtester/api/report?server_name=$host
+        #
         tls_fingerprints: []
         # tls_fingerprints: [{"sha256": "<base64_encoded_sha256_fingerprint>"}]
         """ % locals()