view mod_secure_interfaces/README.markdown @ 4298:020dd0a59f1f

mod_muc_markers: Add option for @id rewriting, default off (may break some clients) XEP-0333 was updated to clarify that stanza-id should be used instead of the 'id' attribute when in a MUC. Some clients still use the id attribute, which is why we were rewriting it. Rewriting is bad because mod_muc advertises stable_id, indicating that Prosody does *not* rewrite ids. Recent versions of Conversations actually depend on this being true. All clients should migrate to using stanza-id for markers. See XEP-0333.
author Matthew Wild <mwild1@gmail.com>
date Mon, 14 Dec 2020 12:09:25 +0000
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
  ------- ---------