Software / code / prosody
Changeset
4233:3c644c3b10e2
prosody.cfg.lua.dist: Add example of 'authentication' option
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 05 Apr 2011 12:36:56 +0100 |
| parents | 4232:582fe508214f |
| children | 4234:ce92aafc9c03 |
| files | prosody.cfg.lua.dist |
| diffstat | 1 files changed, 9 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/prosody.cfg.lua.dist Tue Mar 29 15:07:14 2011 +0100 +++ b/prosody.cfg.lua.dist Tue Apr 05 12:36:56 2011 +0100 @@ -99,6 +99,15 @@ --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
