prosody-modules
d194d1012fd3
mod_s2s_log_certs/README.markdown
Software / code / prosody-modules
File
mod_s2s_log_certs/README.markdown @ 5931:d194d1012fd3
Updating dox for mod_rest. Ideas expressed / clarified:
1) Making clear that mod_rest isn't to be installed under VirtualHosts AND as a component.
2) Understanding some of the implications of this choice:
A) Changes to user authentication
B) How it affects subdomains
3) More consistent use of domain names for clarity.
4) Using different heading sizes to show scope of section.
Essentially, I added all the tidbits I had to clarify in getting this to work in my
own example.
| author | Ben Smith <bens@effortlessis.com> |
|---|---|
| date | Mon, 13 May 2024 13:25:13 -0700 |
| parent | 2876:ea6b5321db50 |
line wrap: on
line source
--- summary: Log certificate status and fingerprint of remote servers ... Introduction ============ This module produces info level log messages with the certificate status and fingerprint every time an s2s connection is established. It can also optionally store this in persistent storage. **info** jabber.org has a trusted valid certificate with SHA1: 11:C2:3D:87:3F:95:F8:13:F8:CA:81:33:71:36:A7:00:E0:01:95:ED Fingerprints could then be added to [mod\_s2s\_auth\_fingerprint](mod_s2s_auth_fingerprint.html). Configuration ============= Add the module to the `modules_enabled` list. modules_enabled = { ... "s2s_log_certs"; } If you want to keep track of how many times, and when a certificate is seen add `s2s_log_certs_persist = true` Compatibility ============= ------- -------------- trunk Works 0.10 Works 0.9 Works 0.8 Doesn't work ------- --------------
