| |||||||||||||
2.6.32.9 Release notes2.6.32.9 Release notesPosted Feb 22, 2010 9:30 UTC (Mon) by dgm (subscriber, #49227)In reply to: 2.6.32.9 Release notes by nelhage Parent article: 2.6.32.9 Release notes
> It just goes to show how difficult it is even for a kernel hacker who follows the kernel closely to figure out which bugs have potential security impact.
This is correct. I would add that given enough time, a determined hacker, and a convenient definition of security, any bug has the potential of having security consequences. Thus, I have to agree with Linus that time spent in assessing if a certain bug is or is not security related is time wasted. Just fix it and move on, or better yet prevent it from happening.
(Log in to post comments)
2.6.32.9 Release notes Posted Feb 22, 2010 14:59 UTC (Mon) by cwarner (guest, #47176) [Link]
If you are knowingly aware it is a security issue your fix may solve the bug but
not the security issue and/or cause another security exploit. Just fixing bugs isn't understanding how a piece of code works in its entirety. Wholeness and correctness for a module is important.
|
|||||||||||||