Package: libpam-pgsql Version: 0.7.3.1-4 Followup-For: Bug #675980 Dear Maintainer,
I used for some time the module to authorize users on mail server. When I started to do it, dovecot begin to fail every few days. I had wrote test app to test authentication for many times it loop. That showed that if user authentication goes through pam-unix it works fine. If take some user that authenticates through pam-pgsql, memory consumption grows indefinitely. Code review showed two problems: 1) on each authentication libgrypt is initialized from scratch (when hash function is called) so about 1K of memory is drained and never returned back. 2) Structure containing module options is never properly freed (app has dirty flow and author preferred to just comment out frees, but even they are not enough as structure has pointers inside that should be freed too). I have patch for second issue and can try to fix first (replacing overwhelming gcrypt with mhash) if someone can conduct thorough testing. -- System Information: Debian Release: 7.2 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.41-042stab083.2 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-pgsql depends on: ii libc6 2.17-97 ii libgcrypt11 1.5.3-3 ii libpam0g 1.1.3-9 ii libpq5 9.3.2-1 libpam-pgsql recommends no packages. libpam-pgsql suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
