apitech
/
prosody
mirror of https://github.com/bjc/prosody
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
IMPORTANT: due to a drive failure, as of 13-Mar-2021, the Mercurial repository had to be re-mirrored, which changed every commit SHA. The old SHAs and trees are backed up in the vault branches. Please migrate to the new branches as soon as you can.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13794 Commits
12 Branches
101 Tags
54 MiB
 
 
 
 
Tag: Branch: Tree: 052d497dee
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '052d497dee'
${ noResults }
prosody/spec/tls
History
Matthew Wild e6849bb76e
spec/tls: Add TLS/certificate integration tests 		9 months ago
..
config1 spec/tls: Add TLS/certificate integration tests 9 months ago
config2 spec/tls: Add TLS/certificate integration tests 9 months ago
config3 spec/tls: Add TLS/certificate integration tests 9 months ago
README spec/tls: Add TLS/certificate integration tests 9 months ago
lib.sh spec/tls: Add TLS/certificate integration tests 9 months ago
run.sh spec/tls: Add TLS/certificate integration tests 9 months ago

README 

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.