Mercurial > prosody-modules
view mod_secure_interfaces/README.markdown @ 4065:92152437ecfe
mod_muc_markers: replace configurable multi-marker tracking with better system
Now tracks a single marker, but automatically applies rules from the XEP about
"higher" markers implying "lower" markers - i.e. "displayed" implies "received".
Still, just a single marker is tracked and synthesized at all times (the one
configured with muc_marker_name).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Tue, 07 Jul 2020 17:08:08 +0100 |
parents | 4d73a1a6ba68 |
children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: 'Mark some network interfaces (e.g. loopback/LAN) as always secure' ... Introduction ============ Sometimes you might run clients without encryption on the same machine or LAN as Prosody - and you want Prosody to treat them as secure (e.g. allowing plaintext authentication) even though they are not encrypted. This module allows you to tell Prosody which of the current server's interfaces (IP addresses) that you consider to be on secure networks. Configuration ============= Configuration is simple, just load the module like any other by adding it to your modules\_enabled list: modules_enabled = { ... "secure_interfaces"; ... } Then set the list of secure interfaces (just make sure it is set in the global section of your config file, and **not** under a VirtualHost or Component): secure_interfaces = { "127.0.0.1", "::1", "192.168.1.54" } Compatibility ============= ------- --------- 0.9 Works 0.8 Unknown trunk Works ------- ---------