aboutsummaryrefslogtreecommitdiffstats
path: root/spec/tls/README
diff options
context:
space:
mode:
authorMatthew Wild <mwild1@gmail.com>2025-04-03 15:14:07 +0100
committerMatthew Wild <mwild1@gmail.com>2025-04-03 15:14:07 +0100
commitb94b7b20b8d5d27bfb7444beb519dfa05ee0bb50 (patch)
treeb8fa5ad7b955d5735bcbd8cc6ab257acf1729d0a /spec/tls/README
parent80d5f64ca0934ea4e3262c9be9c1545e2d0fa273 (diff)
parente6849bb76ee3682ece53d7434bb1e94a89c91cbc (diff)
downloadprosody-b94b7b20b8d5d27bfb7444beb519dfa05ee0bb50.tar.gz
prosody-b94b7b20b8d5d27bfb7444beb519dfa05ee0bb50.zip
Merge 13.0->trunk
Diffstat (limited to 'spec/tls/README')
-rw-r--r--spec/tls/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/spec/tls/README b/spec/tls/README
new file mode 100644
index 00000000..58201728
--- /dev/null
+++ b/spec/tls/README
@@ -0,0 +1,11 @@
+These tests check that SSL/TLS configuration is working as expected.
+
+Just run ./run.sh in this directory (or from the top level,
+`make integration-test-tls`.
+
+Known issues:
+ - The tests do not thorougly clean up after themselves (certs, logs, etc.).
+ This is partly intentional, so they can be inspected in case of failures.
+ - Certs are regenerated every time. Could be smarter about this. But it also
+ helps to guard against incorrect Prosody instances running and hogging the
+ ports, etc.