[Russ Allbery] > Can anyone confirm the comment in the bug log that setuid shouldn't > even be required to do what libgcrypt is doing here, namely locking > memory so that it's not swapped to disk?
Well, I didn't test, but from 'man mlock': | Since Linux 2.6.9, no limits are placed on the amount of memory | that a privileged process can lock and the RLIMIT_MEMLOCK soft | resource limit instead defines a limit on how much memory an | unprivileged process may lock. On my system 'ulimit -l' (max locked memory) shows 64 kB, which, you know, ought to be enough for anybody. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100309003921.go18...@p12n.org
