From: "Hanno Böck" <hanno@hboeck.de>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] 2015 kernel CVEs
Date: Wed, 20 Jan 2016 18:48:08 +0100 [thread overview]
Message-ID: <20160120184808.3a5c6d26@pc1> (raw)
In-Reply-To: <CAO4UgPQxZg7QT0QiE9G4VBenBG55KVNomNCWOZ5_CEdbmEUSTA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Wed, 20 Jan 2016 14:15:14 +0000
Wade Mealing <wmealing@gmail.com> wrote:
> I'm all about improving process, I imagine I would have done the same
> steps. What changes to the responses would need to be made to be
> less limited ? Understand that i'm not taking this personally and
> consider this an opportunity for Red Hat Security to improve as a
> group.
Just to make this clear, I was not involved at all. I based my
statement purely on publicly available information from the advisory
that says:
"We unsuccessfully tried to contact the vendor for several months. We
never received any response on our bugtraq ticket:"
So I'm not the right person to discuss what went wrong in the process.
FWIW I tried to reach out to one of the people doing this research
(Sergej Schumilo) and hope we can make sure these issues get tackled.
--
Hanno Böck
http://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: BBB51E42
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-20 17:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:28 2015 kernel CVEs Dan Carpenter
2016-01-19 11:28 ` [kernel-hardening] " Dan Carpenter
2016-01-19 11:49 ` Hanno Böck
2016-01-19 15:49 ` Quentin Casasnovas
2016-01-20 11:19 ` Hanno Böck
2016-01-20 14:15 ` Wade Mealing
2016-01-20 17:48 ` Hanno Böck [this message]
2016-01-19 13:13 ` Wade Mealing
2016-01-19 14:56 ` One Thousand Gnomes
2016-01-19 14:56 ` [kernel-hardening] " One Thousand Gnomes
2016-01-19 16:32 ` [kernel-hardening] " Ben Hutchings
2016-01-19 17:54 ` Greg KH
2016-01-20 17:05 ` Ben Hutchings
2016-01-20 18:04 ` Greg KH
2016-01-21 15:18 ` Jiri Kosina
2016-01-21 18:46 ` Ben Hutchings
2016-01-19 16:57 ` Peter Hurley
2016-01-19 16:57 ` [kernel-hardening] " Peter Hurley
2016-01-19 17:00 ` Josh Boyer
2016-01-19 17:00 ` [kernel-hardening] " Josh Boyer
2016-01-19 17:51 ` Greg KH
2016-01-19 17:51 ` [kernel-hardening] " Greg KH
2016-01-20 7:12 ` Marcus Meissner
2016-01-19 17:57 ` [kernel-hardening] " Theodore Ts'o
2016-01-19 18:00 ` Al Viro
2016-01-19 18:00 ` [kernel-hardening] " Al Viro
2016-01-19 22:41 ` Eric W. Biederman
2016-01-19 22:47 ` [kernel-hardening] " Eric W. Biederman
2016-01-20 20:11 ` Jann Horn
2016-01-20 21:26 ` One Thousand Gnomes
2016-01-19 23:35 ` Kees Cook
2016-01-19 23:35 ` Kees Cook
2016-01-20 9:57 ` Miroslav Benes
2016-01-20 9:57 ` [kernel-hardening] " Miroslav Benes
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=20160120184808.3a5c6d26@pc1 \
--to=hanno@hboeck.de \
--cc=kernel-hardening@lists.openwall.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.