| Server IP : 23.254.227.96 / Your IP : 216.73.216.7 Web Server : Apache/2.4.62 (Unix) OpenSSL/1.1.1k System : Linux hwsrv-1277026.hostwindsdns.com 4.18.0-477.13.1.el8_8.x86_64 #1 SMP Tue May 30 14:53:41 EDT 2023 x86_64 User : viralblo ( 1001) PHP Version : 8.1.31 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /proc/self/root/usr/share/doc/dovecot/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 2019-06-19 12:42)