Package: gringotts Version: 1.2.8-8 Followup-For: Bug #299566 I had the same problem. I did think to look at README.Debian, but it was not apparent that it was at all related to the errors I was getting. I am still not sure whether my system is more or less secure now and whether I should be feeling better or worse. The pam changes don't take effect until the next login, so making the changes in README.Debian doesn't seem to help at first - and since it wasn't obviously the same problem in the first place I was left in a very confused state.
I recommend that the program check for sufficient memlock ability and give a sensible error in the insufficient case. Even better, start without locking memory and displaying an error indicating what is going on and the solution. In the absence of that solution, more explicit documentation would be good. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (800, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages gringotts depends on: ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libglib2.0-0 2.6.3-1 The GLib library of C routines ii libgringotts1 1.2.1-2 encapsulate data in an encrypted a ii libgtk2.0-0 2.6.2-4 The GTK+ graphical user interface ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libpopt0 1.7-5 lib for parsing cmdline parameters -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
