NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Huh? (Score:2)
That's interesting. The "macro admin security fix" is something I don't understand, but the first two should be no brainers. Why the heck can't they figure that out for themselves? I do understand your reluctance to get specific about "here's how you attack unpatched versions of this software."
Not that far-fetched (Score:1)
I don’t see what’s so unusual about the request. Figuring out the issues requires study of the source code, and evaluating them to figure out what follows from them is often unclear to someone without a good understanding of the codebase. This has been a point of tension between the Linux kernelhackers and distributors, who often can’t tell how significant a bugfix really is without either being told or investing significant effort of their own.
Let’s take a look at the questions:
Re: (Score:2)
Fair enough. I stand correct :)
Re: (Score:2)
Er, corrected!
Re:Not that far-fetched (Score:1)
Don’t worry, after all these times I wrote “privile d ge” in that comment, your transgression is quite minor. Ugh. *hides in shame*
Reply to This
Parent