Your message dated Wed, 9 Jul 2008 15:41:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line ulimits set by kernel and respected by PAM now
has caused the Debian Bug report #340018,
regarding libpam-modules: default ulimit for Debian
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
340018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340018
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libpam-modules
Version: 0.76-22
Severity: normal
I am not sure the reason a users proccess limit is set to 'unlimited' by default
but it seems easy for any user with access to a compiler can crash a debain
system with a
forkbomb, or flood it with zombie proccesses. Shouldn't a user have some sort
of limit imposed?
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages libpam-modules depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libdb3 3.2.9-22 Berkeley v3 Database Libraries [ru
ii libpam0g 0.76-22 Pluggable Authentication Modules l
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.99.7.1-2
The kernel sets reasonable ulimits now, based on available physical
memory. Recent PAM respects these limits, and sets them correctly when
starting a session.
--
Kees Cook @outflux.net
--- End Message ---
