Mercurial > dovecot > original-hg > dovecot-1.2
changeset 8678:d9c28e76ef97 HEAD
Don't use clean_pool with login processes.
The previous fix for clean_pool perhaps might have fixed all the bugs
related to it, but since it only produces extra work with no real benefit,
just don't use it. The original idea behind using it was flawed.
| author | Timo Sirainen <tss@iki.fi> |
|---|---|
| date | Fri, 23 Jan 2009 13:13:15 -0500 |
| parents | 61dd475e9f0a |
| children | 418a6b109238 |
| files | src/login-common/main.c |
| diffstat | 1 files changed, 0 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/src/login-common/main.c Fri Jan 23 13:12:50 2009 -0500 +++ b/src/login-common/main.c Fri Jan 23 13:13:15 2009 -0500 @@ -413,13 +413,6 @@ fd_debug_verify_leaks(i, 1024); } #endif - /* clear all allocated memory before freeing it. this makes the login - processes pretty safe to reuse for new connections since the - attacker won't be able to find anything interesting from the - memory. */ - default_pool = system_clean_pool; - data_stack_set_clean_after_pop(TRUE); - /* NOTE: we start rooted, so keep the code minimal until restrict_access_by_env() is called */ lib_init();