Jeff Taylor | January 30, 2004
Microsoft has stepped up with a $250,000 bounty for the skin of the author of the MyDoom.B email virus. Sounds interesting, but is there any evidence that such cyber-bounties produce positive results?
I mean, the people who build these kinds of things might be more motivated by the prospect of big, fat bounty on their weaselly little heads than other folks might be moved by a reward in exchange for stopping said weasels. Could make the problem worse. That's why I say the only safe recourse is shoot-on-sight.
Help Reason celebrate its next 40 years. Donate Now!
Try Reason's award-winning print edition today! Your first issue is FREE if you are not completely satisfied.
Why doesn't Microsoft pay a $250K reward to it's own programmers
who discover and close vulnerabilities within MS software?
It would probably have a better net effect.
Microsoft doesn't make money by fixing bugs. They make money by selling new whizbang features. I think these virus bounties are mostly PR, but after a few haXor d3wdz fink out their buddies, the bounties will have created a nice deterrent. Note that this does NOT mean Microsoft software will be more secure! It just means that the truly evil or "professional" hackers will keep security holes to themselves (like Microsoft's NSA_KEY cryptography backdoor).
Why doen't the Department of Homeland Security fine Microsoft $250k and use it to pay for the US-CERT virus alert system.
Joe - you may have been being facetious, but schemes like that
have been tried. The problem is that they create an incentive for
programmers to create bugs in their programs so they can "find"
them later and claim the bounty. Assuming, of course, that an MS
programmer is smart enough to know whether or not he's creating a
security hole.
More seriously, Joel Spolsky (of joelonsoftware.com) has written a
bit on the Microsoft practice of having an individual programmer
"own" certain code or functionality. It's usually portrayed as a
good thing, but I wonder if it doesn't have negative implications
in terms of getting more eyeballs on a given piece of code.
Site comments/questions:
Media Inquiries and Reprint Permissions:
(310) 367-6109
Editorial & Production Offices:
3415 S. Sepulveda Blvd.
Suite 400
Los Angeles, CA 90034
(310) 391-2245