From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Steve Bergman <steve@rueb.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proper procedure for reporting possible security vulnerabilities?
Date: Tue, 11 Jan 2005 16:10:57 +0000 [thread overview]
Message-ID: <1105457773.15793.28.camel@localhost.localdomain> (raw)
In-Reply-To: <41E2F6B3.9060008@rueb.com>
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
cert
dfn-cert
any other cert like object
security@almost any linux vendor
but didn't. Nor it appears did they chase up their report.
next prev parent reply other threads:[~2005-01-11 18:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 16:46 Proper procedure for reporting possible security vulnerabilities? Steve Bergman
2005-01-10 18:23 ` Indrek Kruusa
2005-01-10 19:24 ` Alan Cox
2005-01-11 9:32 ` Florian Weimer
2005-01-10 21:31 ` Florian Weimer
2005-01-10 21:42 ` Steve Bergman
2005-01-10 22:08 ` Diego Calleja
2005-01-11 0:19 ` Barry K. Nathan
2005-01-11 0:45 ` Diego Calleja
2005-01-11 9:35 ` Florian Weimer
2005-01-11 16:57 ` Jesper Juhl
2005-01-11 17:05 ` Jan Engelhardt
2005-01-10 22:09 ` linux-os
2005-01-11 0:44 ` Barry K. Nathan
2005-01-10 22:11 ` Jesper Juhl
2005-01-11 0:40 ` Chris Wright
2005-01-11 1:09 ` Diego Calleja
2005-01-11 1:18 ` Chris Wright
2005-01-11 17:05 ` Jesper Juhl
2005-01-11 16:39 ` Alan Cox
2005-01-11 21:25 ` Jesper Juhl
2005-01-11 21:29 ` Chris Wright
2005-01-12 21:05 ` Jesper Juhl
2005-01-17 22:49 ` Werner Almesberger
2005-01-17 22:52 ` Chris Wright
2005-01-17 23:23 ` Christoph Hellwig
2005-01-17 23:26 ` Chris Wright
2005-01-17 23:57 ` Alan Cox
2005-01-18 1:08 ` Chris Wright
2005-01-11 17:57 ` Chris Wright
2005-01-12 12:23 ` Florian Weimer
2005-01-11 9:49 ` Florian Weimer
2005-01-11 16:10 ` Alan Cox [this message]
2005-01-12 12:33 ` Florian Weimer
2005-01-13 15:36 ` Alan Cox
[not found] <200501101959.j0AJxUvl032294@laptop11.inf.utfsm.cl>
2005-01-10 21:36 ` Indrek Kruusa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1105457773.15793.28.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@rueb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.