* New upstream release. - Add support for NSS groups to pam_group. Closes: #589019, LP: #297408. - Support cross-building the package. Thanks to Neil Williams <codehelp@debian.org> for the patch. Closes: #284854. * debian/rules: pass getconf LFS_CFLAGS so that we get a 64-bit rlimit interface. Closes: #579402. * Drop patches conditional_module,_conditional_man and mkhomedir_linking.patch, which are included upstream. * debian/patches/hurd_no_setfsuid: pam_env and pam_mail now also use setfsuid, so patch them to be likewise Hurd-safe. * Update debian/source.lintian-overrides to clean up some spurious warnings. * debian/libpam-modules.postinst: if any 'min=n' options are found in /etc/pam.d/common-password, convert them on upgrade to 'minlen=n' for compatibility with upstream. * debian/NEWS: document the disappearance of 'min=n', in case users have encoded this option elsewhere outside of /etc/pam.d/common-password. * debian/patches/007_modules_pam_unix: drop compatibility handling of 'max=' no-op; use of this option will now log an error, as warned three years ago. * Bump Standards-Version to 3.9.1. * Add lintian overrides for a few more spurious warnings. * debian/patches-applied/no_PATH_MAX_on_hurd: define PATH_MAX for compatibility when it's not already set. Closes: #552043. * debian/local/pam-auth-update: Don't try to pass embedded newlines to debconf; backslash-escape them instead and use CAPB escape. * debian/local/pam-auth-update: sort additional module options before writing them out, so that we don't wind up with a different config file on every invocation. Thanks to Jim Paris <jim@jtan.com> for the patch. Closes: #594123. * debian/libpam-runtime.{postinst,templates}: since 1.1.2-1 is targeted for post-squeeze, we don't need to support upgrades from 1.0.1-6 to 1.0.1-10 anymore. Drop the debconf error note about having configured your system with a lack of authentication, so that translators don't spend any more time on it. * Updated debconf translations: - Swedish, thanks to Martin Bagge <brother@bsnet.se> (closes: #575875)
\fIvalueN\fR\'s not mentioned explicitly\&. Note, the full list of PAM errors is available in
379
379
\FC/usr/include/security/_pam_types\&.h\F[]\&. The
380
380
\fIactionN\fR
381
can be: an unsigned integer,
382
\fIn\fR, signifying an action of \'jump over the next
383
\fIn\fR
384
modules in the stack\'; or take one of the following forms:
381
can take one of the following forms:
385
382
.PP
386
383
ignore
387
384
.RS 4
409
406
equivalent to ok with the side effect of terminating the module stack and PAM immediately returning to the application\&.
410
407
.RE
411
408
.PP
409
N (an unsigned integer)
410
.RS 4
411
equivalent to ok with the side effect of jumping over the next N modules in the stack\&. Note that N equal to 0 is not allowed (and it would be identical to ok in such case)\&.
412
.RE
413
.PP
412
414
reset
413
415
.RS 4
414
416
clear all memory of the state of the module stack and start again with the next stacked module\&.