From dddc15e0d925ced049794b46f5132ad68e7bf7ae Mon Sep 17 00:00:00 2001 From: Matthew Wild Date: Tue, 5 Apr 2011 12:36:56 +0100 Subject: prosody.cfg.lua.dist: Add example of 'authentication' option --- prosody.cfg.lua.dist | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'prosody.cfg.lua.dist') diff --git a/prosody.cfg.lua.dist b/prosody.cfg.lua.dist index d1bd7d67..e513b116 100644 --- a/prosody.cfg.lua.dist +++ b/prosody.cfg.lua.dist @@ -99,6 +99,15 @@ ssl = { --c2s_require_encryption = false --s2s_require_encryption = false +-- Select the authentication backend to use. The 'internal' providers +-- use Prosody's configured data storage to store the authentication data. +-- To allow Prosody to offer secure authentication mechanisms to clients, the +-- default provider stores passwords in plaintext. If you do not trust your +-- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed +-- for information about using the hashed backend. + +authentication = "internal_plain" + -- Select the storage backend to use. By default Prosody uses flat files -- in its configured data directory, but it also supports more backends -- through modules. An "sql" backend is included by default, but requires -- cgit v1.2.3