Software / code / prosody
Changeset
5573:ca9f99f7dcbc
prosody.cfg.lua.dist: Fix my s2s_secure(_auth) mess
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Sat, 11 May 2013 13:54:02 +0100 |
| parents | 5571:ae9672f4079a |
| children | 5574:40fe8bd35eaa 5576:7656b9f06bb5 |
| files | prosody.cfg.lua.dist |
| diffstat | 1 files changed, 6 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/prosody.cfg.lua.dist Fri May 10 22:29:03 2013 +0200 +++ b/prosody.cfg.lua.dist Sat May 11 13:54:02 2013 +0100 @@ -99,20 +99,21 @@ -- Force certificate authentication for server-to-server connections? -- This provides ideal security, but requires servers you communicate -- with to support encryption AND present valid, trusted certificates. +-- NOTE: Your version of LuaSec must support certificate verification! -- For more information see http://prosody.im/doc/s2s#security -s2s_secure = true +s2s_secure_auth = false -- Many servers don't support encryption or have invalid or self-signed -- certificates. You can list domains here that will not be required to -- authenticate using certificates. They will be authenticated using DNS. --- s2s_insecure_domains = { "gmail.com" } +--s2s_insecure_domains = { "gmail.com" } --- Even if you leave s2s_secure disabled, you can still require it for --- some domains by specifying a list here. +-- Even if you leave s2s_secure_auth disabled, you can still require valid +-- certificates for some domains by specifying a list here. --- s2s_secure_domains = { "jabber.org" } +--s2s_secure_domains = { "jabber.org" } -- Select the authentication backend to use. The 'internal' providers -- use Prosody's configured data storage to store the authentication data.
