diff options
| author | Steve Langasek <vorlon@debian.org> | 2009-03-02 02:51:27 -0800 |
|---|---|---|
| committer | Steve Langasek <vorlon@debian.org> | 2019-01-08 17:27:15 -0800 |
| commit | 6e7d2d658dfbbb84f6c7727c3bcf56efe6872a9e (patch) | |
| tree | 356d3a7cdfd5e4eb91918ddab78a8b7db70cad4d | |
| parent | 987fbc2a1b293b576408535446aac8d2573744ec (diff) | |
prettify the changelog
| -rw-r--r-- | debian/changelog | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/debian/changelog b/debian/changelog index 70f34833..1bd70490 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,13 +1,13 @@ pam (1.0.1-7) UNRELEASED; urgency=low - * 027_pam_limits_better_init_allow_explicit_root: RLIM_INFINITY may or may - not be invalid for RLIMIT_NOFILE, but we don't want to set a hard limit - of 1024 by default; try to set this limit to the value of - /proc/sys/fs/nr_open if we can, or fall back to RLIM_INFINITY. - Closes: #515673, LP: #327597. - * 027_pam_limits_better_init_allow_explicit_root: also fix the patch so - that our limit resets are actually *applied*, which has apparently been - broken for who knows how long! + * 027_pam_limits_better_init_allow_explicit_root: + - RLIM_INFINITY may or may not be invalid for RLIMIT_NOFILE, but we + don't want to set a hard limit of 1024 by default; try to set this + limit to the value of /proc/sys/fs/nr_open if we can, or fall back + to RLIM_INFINITY. Closes: #515673, LP: #327597. + - also fix the patch so that our limit resets are actually + *applied*, which has apparently been broken for who knows how + long! - shadow the finite kernel defaults for RLIMIT_SIGPENDING and RLIMIT_MSGQUEUE as well, so that the preceding changes don't suddenly expose systems to DoS or other issues. |