First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 215000
Alias:
Product:
Component:
Status: NEW
Resolution:
Assigned To: Gentoo Security <security@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Robert Buchholz <rbu@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:
Flags: Requestee:
 
 
  ()

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 215000 depends on: Show dependency tree
Bug 215000 blocks:

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.








View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-03-27 01:14 0000 
As discovered here today, the change in Kernel 2.6.17 intended to inhibit
users from setting RLIMIT_CPU to 0 (as that is equivalent to unlimited) by
"cheating" and setting it to 1 in such a case, does not make a difference,
as the check is done in the wrong place (too late), and only applies to the
profiling code.

Bugs:
  https://launchpad.net/bugs/107209
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419706

Fixed in 2.6.22:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9926e4c74300c4b31dee007298c6475d33369df0

------- Comment #1 From unnamedrambler@gmail.com 2008-03-27 17:00:59 0000 ------- 
proposed

[linux >= 2.6.17 < 2.6.22]
9926e4c74300c4b31dee007298c6475d33369df0

------- Comment #2 From Robert Buchholz 2008-03-27 20:55:55 0000 ------- 
sounds good :-)
First Last Prev Next    No search results available      Search page      Enter new bug