view mod_telnet_tlsinfo/README.markdown @ 3955:017f60608fc8

mod_smacks: also count outgoing MAM messages mod_smacks doesn't count outgoing MAM messages, which causes warnings in Prosody such as: > The client says it handled 41 new stanzas, but we only sent 2 It seems mod_smacks is in the wrong here and that it's too strict in trying to determine what is a valid stanza to count. In RFC6120: > Definition of XML Stanza: An XML stanza is the basic unit of meaning > in XMPP. A stanza is a first-level element (at depth=1 of the stream) > whose element name is "message", "presence", or "iq" and whose > qualifying namespace is 'jabber:client' or 'jabber:server'.
author JC Brand <jc@opkode.com>
date Thu, 26 Mar 2020 11:57:02 +0100
parents 957e87067231
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
  --------------------- ------------------