Re: Proper procedure for reporting possible security vulnerabilities?

[Florian Weimer]

* Alan Cox:

> On Llu, 2005-01-10 at 21:42, Steve Bergman wrote:
>> handled.  They clam that they sent email to Linus and Andrew and did not 
>> receive a response for 3 weeks, and that is why they released exploit 
>> code into the wild.
>> 
>> Anyone here have any comments on what I should tell him?
>
> They could have reported them to:
> 	vendor-sec

vendor-sec's reputation apparently has been damaged in some circles as
the result of the fake e-matters advisory.  Heise Online also
suggested that the exploit was leaked from vendor-sec ("a natural
conclusion").

> 	cert

CERT/CC shares vulnerability information with anyone who's paying
enough money (read the fine print).  Probably that's not what the
submitters want.

> 	dfn-cert

DFN-CERT is certainly honored to be included in this list, but they
can only forward it to security@ at some vendors and probably
vendor-sec.

If you get stuck, asking someone who has published kernel
vulnerabilities previously what to do is also an option.

But in general, there are plenty of options besides trying to contact
just two kernel developers high up the food chain.  Contacting the
subsystem maintainer is often a possiblity, too.  Of course, it's no
good if the subsystem maintainer tells you to post it to a public
list. 8-/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/