Mercurial > prosody-modules
view mod_telnet_tlsinfo/README.md @ 6319:04c3273cb81f
mod_auth_cyrus: Add empty 'profile' table to SASL handler objects
This is for compatibility with Prosody's built-in util.sasl objects.
A SASL profile table usually includes methods supported by the backend, which
can be used by SASL mechanism handlers to perform operations (such as testing
the password). It also optionally contains a 'cb' field with channel binding
method handlers.
The Cyrus backend doesn't support channel binding, and doesn't have the same
concept of auth backend methods (it handles all that internally, and Prosody
has no insight or control over it).
Thus, we create an empty profile which informs Prosody that the SASL handler
does not support any of the auth or channel binding methods. Some features
will not work, but they didn't work anyway. This just makes it explicit.
This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to
always contain a 'profile' field.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Thu, 04 Sep 2025 10:14:46 +0100 |
| parents | fe081789f7b5 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Obsolete' summary: Telnet command for showing TLS info --- Introduction ============ This module adds two commands to the telnet console, `c2s:showtls()` and `s2s:showtls()`. These commands shows TLS parameters, such as ciphers and key agreement protocols, of all c2s or s2s connections. Configuration ============= Just add the module to the `modules_enabled` list. There is no other configuration. modules_enabled = { ... "telnet_tlsinfo"; } Usage ===== Simply type `c2s:showtls()` to show client connections or `s2s:showtls()` for server-to-server connections. These commands can also take a JID for limiting output to matching users or servers. s2s:showtls("prosody.im") | example.com -> prosody.im | protocol: TLSv1.1 | cipher: DHE-RSA-AES256-SHA | encryption: AES(256) | algbits: 256 | bits: 256 | authentication: RSA | key: DH | mac: SHA1 | export: false Field Description ---------------- ------------------------------------------------------------------------------------------------- protocol The protocol used. **Note**: With older LuaSec, this is the protocol that added the used cipher cipher The OpenSSL cipher string for the currently used cipher encryption Encryption algorithm used bits, algbits Secret bits involved in the cipher authentication The authentication algorithm used mac Message authentication algorithm used key Key exchange mechanism used. export Whethere an export cipher is used Compatibility ============= --------------------- ------------------ 0.9 with LuaSec 0.5 Works 0.10 Merged into core --------------------- ------------------
