Difference between revisions of "Qpsmtpd:auth/auth flat file"
From SME Server
Jump to navigationJump to search (Created page with "<span id="_top">Qpsmtpd#Plugins</span> = NAME = authdeny = SYNOPSIS = This plugin doesn't actually check anything and will fail any user no matt...") |
|||
Line 2: | Line 2: | ||
= [[#___top|NAME]] = | = [[#___top|NAME]] = | ||
− | + | auth_flat_file - simple CRAM MD5 auth plugin using a flat password file | |
= [[#___top|SYNOPSIS]] = | = [[#___top|SYNOPSIS]] = | ||
− | + | in config/plugins: | |
− | < | + | <pre> auth/auth_flat_file</pre> |
− | + | in config/flat_auth_pw | |
− | + | ||
− | + | <pre> username1:password1 | |
− | [[ | + | username2:password2 |
− | + | ...</pre> | |
− | + | = [[#___top|DESCRIPTION]] = | |
− | |||
+ | This plugin implements a very simple authentication plugin using a flat password file containing username and password separated by colons. | ||
+ | Note that this plugin enforces the use of a full email address (including @domain) as the username. There's no particular reason for this so feel free to modify the code to suit your setup. | ||
− | + | The password is stored on disk unencrypted, however authentication uses a HMAC algorithm so no password is transfered in the clear. | |
− | <!-- Generated Mon Apr 8 09:24: | + | <!-- Generated Mon Apr 8 09:24:49 EDT 2019 using |
perldoc -T -ohtml $plugins/$1 \|pandoc -f html -t mediawiki \|sed '1 i\\n\n\n<span id="_top">[[Qpsmtpd#Plugins]]</span>' \|sed -e 's#</d.>##' | perldoc -T -ohtml $plugins/$1 \|pandoc -f html -t mediawiki \|sed '1 i\\n\n\n<span id="_top">[[Qpsmtpd#Plugins]]</span>' \|sed -e 's#</d.>##' | ||
--> | --> | ||
---- | ---- | ||
− | [[Category:Qpsmtpd| | + | [[Category:Qpsmtpd|auth/auth_flat_file]] |
Latest revision as of 14:25, 8 April 2019
NAME
auth_flat_file - simple CRAM MD5 auth plugin using a flat password file
SYNOPSIS
in config/plugins:
auth/auth_flat_file
in config/flat_auth_pw
username1:password1 username2:password2 ...
DESCRIPTION
This plugin implements a very simple authentication plugin using a flat password file containing username and password separated by colons.
Note that this plugin enforces the use of a full email address (including @domain) as the username. There's no particular reason for this so feel free to modify the code to suit your setup.
The password is stored on disk unencrypted, however authentication uses a HMAC algorithm so no password is transfered in the clear.