Bug#546397: pwsafe: Complains about not being setuid despite availability of mlock() to unprivileged processes

2010-04-23 Thread Jason White
Iustin Pop wrote: > Pwsafe does the right thing here. mlock default limit is 64K, and pwsafe > binary requests (on my system) 69K. After increase the memlock limit, > there are no warnings anymore. Thank you; that fixed it. Perhaps it merits a note in the README file. Regards, Jason. --

Bug#546397: pwsafe: Complains about not being setuid despite availability of mlock() to unprivileged processes

2010-04-23 Thread Iustin Pop
On Sun, Sep 13, 2009 at 11:52:28AM +1000, Jason White wrote: > Package: pwsafe > Version: 0.2.0-3 > Severity: normal > > > Pwsafe issues warnings about its not being a setuid binary. However, since > kernel 2.6.8, according to the mlock(2) manual page, the mlock() function is > available to unpri

Bug#546397: pwsafe: Complains about not being setuid despite availability of mlock() to unprivileged processes

2009-09-12 Thread Jason White
Package: pwsafe Version: 0.2.0-3 Severity: normal Pwsafe issues warnings about its not being a setuid binary. However, since kernel 2.6.8, according to the mlock(2) manual page, the mlock() function is available to unprivileged processes within limits that can be specified by ulimit. Pwsafe shou