path: root/debian/patches-applied/027_pam_limits_better_init_allow_explicit_root
Commit message (Expand)AuthorAge
* Refresh patchesSteve Langasek2022-08-17
* Refresh patchesSteve Langasek2019-01-24
* Refresh patchesSteve Langasek2019-01-08
* make sure we're passing ctrl to the function if we need to check PAM_DEBUGSteve Langasek2019-01-08
* debian/patches-applied/027_pam_limits_better_init_allow_explicit_root:Steve Langasek2019-01-08
* * debian/patches-applied/027_pam_limits_better_init_allow_explicit_root:Kees Cook2019-01-08
* debian/patches-applied/027_pam_limits_better_init_allow_explicit_root:Steve Langasek2019-01-08
* update the existing 027_pam_limits_better_init_allow_explicit_root patchSteve Langasek2019-01-08
* Include changes to pam_limits/README in the patch, since they end up in theSteve Langasek2019-01-08
* refresh other patches for new upstream releaseSteve Langasek2019-01-08
* 027_pam_limits_better_init_allow_explicit_root: defaults need to beSteve Langasek2019-01-08
* 027_pam_limits_better_init_allow_explicit_root: set the RLIMIT_MEMLOCKSteve Langasek2019-01-08
* include documentation in the patch, giving examples of how to set Steve Langasek2019-01-08
* revert the 'fix' for bug #515673, since this isn't really a bug at all.Steve Langasek2019-01-08
* shadow the finite kernel defaults for RLIMIT_SIGPENDING andSteve Langasek2019-01-08
* 027_pam_limits_better_init_allow_explicit_root: also fix the patch soSteve Langasek2019-01-08
* 027_pam_limits_better_init_allow_explicit_root: RLIM_INFINITY may or maySteve Langasek2019-01-08
* refresh patches for new upstream versionSteve Langasek2019-01-03
* 027_pam_limits_better_init_allow_explicit_root: RLIM_INFINITY is alsoSteve Langasek2019-01-03
* refresh patches for new upstream versionSteve Langasek2019-01-03
* fix-up commit for grafting svn history onto git historySteve Langasek2019-01-02