|
Server : Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 System : Linux server.jackjohnson.com 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug 24 01:07:11 UTC 2012 x86_64 User : jackjohn ( 502) PHP Version : 5.3.17 Disable Function : NONE Directory : /usr/share/doc/dovecot-2.2.23/wiki/ |
Upload File : |
Security tuning
===============
Dovecot is pretty secure out-of-the box. It uses multiple processes and
privilege separation to isolate different parts from each others in case a
security hole is found from one part.
Some things you can do more:
* Allocate each user their own UID and GID (see <UserIds.txt>)
* Use a separate /dovecot-auth/ user for authentication process (see
<UserIds.txt>)
* You can chroot authentication and mail processes (see <Chrooting.txt>)
* Compiling Dovecot with garbage collection ('--with-gc' configure option)
fixes at least in theory any security holes caused by double free()s.
However this hasn't been tested much and there may be problems.
* There are some security related SSL settings (see
<SSL.DovecotConfiguration.txt>)
* Set 'first/last_valid_uid/gid' settings to contain only the range actually
used by mail processes
(This file was created from the wiki on 2016-03-30 04:43)