Software / code / prosody-modules
Comparison
mod_secure_interfaces/README.markdown @ 1803:4d73a1a6ba68
Convert all wiki pages to Markdown
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Fri, 28 Aug 2015 18:03:58 +0200 |
| parent | 1782:mod_secure_interfaces/README.wiki@29f3d6b7ad16 |
comparison
equal
deleted
inserted
replaced
| 1802:0ab737feada6 | 1803:4d73a1a6ba68 |
|---|---|
| 1 --- | |
| 2 labels: | |
| 3 - 'Stage-Beta' | |
| 4 summary: 'Mark some network interfaces (e.g. loopback/LAN) as always secure' | |
| 5 ... | |
| 6 | |
| 7 Introduction | |
| 8 ============ | |
| 9 | |
| 10 Sometimes you might run clients without encryption on the same machine | |
| 11 or LAN as Prosody - and you want Prosody to treat them as secure (e.g. | |
| 12 allowing plaintext authentication) even though they are not encrypted. | |
| 13 | |
| 14 This module allows you to tell Prosody which of the current server's | |
| 15 interfaces (IP addresses) that you consider to be on secure networks. | |
| 16 | |
| 17 Configuration | |
| 18 ============= | |
| 19 | |
| 20 Configuration is simple, just load the module like any other by adding | |
| 21 it to your modules\_enabled list: | |
| 22 | |
| 23 modules_enabled = { | |
| 24 ... | |
| 25 "secure_interfaces"; | |
| 26 ... | |
| 27 } | |
| 28 | |
| 29 Then set the list of secure interfaces (just make sure it is set in the | |
| 30 global section of your config file, and **not** under a VirtualHost or | |
| 31 Component): | |
| 32 | |
| 33 secure_interfaces = { "127.0.0.1", "::1", "192.168.1.54" } | |
| 34 | |
| 35 Compatibility | |
| 36 ============= | |
| 37 | |
| 38 ------- --------- | |
| 39 0.9 Works | |
| 40 0.8 Unknown | |
| 41 trunk Works | |
| 42 ------- --------- |