⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.133
Server IP:
185.119.109.197
Server:
Linux managedhosting.chostar.me 5.15.0-160-generic #170-Ubuntu SMP Wed Oct 1 10:06:56 UTC 2025 x86_64
Server Software:
Apache
PHP Version:
8.1.33
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
usr
/
share
/
doc
/
dovecot-core
/
wiki
/
View File Name :
SecurityTuning.txt
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)