File

mod_auth_ccert/README.markdown @ 5173:460f78654864

mod_muc_rtbl: also filter messages This was a bit tricky because we don't want to run the JIDs through SHA256 on each message. Took a while to come up with this simple plan of just caching the SHA256 of the JIDs on the occupants. This will leave some dirt in the occupants after unloading the module, but that should be ok; once they cycle the room, the hashes will be gone. This is direly needed, otherwise, there is a tight race between the moderation activities and the actors joining the room.
author Jonas Schäfer <jonas@wielicki.name>
date Tue, 21 Feb 2023 21:37:27 +0100
parent 4433:0e3f5f70a51d
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
- 'Type-Auth'
summary: Client Certificate authentication module
...

Introduction
============

This module implements PKI-style client certificate authentication. You
will therefore need your own Certificate Authority. How to set that up
is beyond the current scope of this document.

Configuration
=============


    authentication = "ccert"
    certificate_match = "xmppaddr" -- or "email"

    c2s_ssl = {
        cafile = "/path/to/your/ca.pem";
        capath = false; -- Disable capath inherited from built-in default
        verify = {"peer"; "client_once"}; -- Ask for client certificate
        verifyext = {
            -- Don't validate client certs as if they were server certs
            lsec_ignore_purpose = false
        }
    }


Compatibility
=============

  ----------------- --------------
  trunk             Works
  0.10 and later    Works
  0.9 and earlier   Doesn't work
  ----------------- --------------