From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking
Date: Mon, 9 Jun 2014 19:57:15 -0700 [thread overview]
Message-ID: <20140610025715.GA24314@kroah.com> (raw)
In-Reply-To: <CALCETrWYvQR5QRg7_tG3ZFk7dy0X7Ji50Lgxt81aqjjsxS7gCg@mail.gmail.com>
On Mon, Jun 09, 2014 at 05:51:37PM -0700, Andy Lutomirski wrote:
> [cc list trimmed, security@ added]
>
> On Mon, Jun 9, 2014 at 5:31 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Jun 09, 2014 at 07:35:57PM -0400, Josh Boyer wrote:
> >> On Mon, Jun 9, 2014 at 6:46 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> >
> >> > But yes, having something "real" might be good if the load gets higher,
> >> > right now it's so low that my "sweep pending security patches" task
> >> > usually catches anything pending, which is rare.
> >>
> >> How does one get added to the security@ alias? We've been carrying
> >> this patch in Fedora for a bit now. I'd be happy to help track things
> >> given we get distro security bug reports and such.
> >
> > Just ask on the security@ alias to be added and we can take it from
> > there.
> >
>
> Would it make sense for there to be someone on the security list who
> can assign CVE numbers?
I'm pretty sure we have that already.
thanks,
greg k-h
next prev parent reply other threads:[~2014-06-10 2:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 3:09 [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking Eric Paris
2014-05-29 3:09 ` [PATCH 2/2] audit: do not select HAVE_ARCH_AUDITSYSCALL on x32 Eric Paris
2014-06-09 22:30 ` [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking Greg KH
2014-06-09 22:35 ` Andy Lutomirski
2014-06-09 22:46 ` Greg KH
2014-06-09 22:55 ` Andy Lutomirski
2014-06-10 0:32 ` Greg KH
2014-06-10 0:30 ` Andy Lutomirski
2014-06-10 0:37 ` Greg KH
2014-06-09 23:35 ` Josh Boyer
2014-06-10 0:31 ` Greg KH
2014-06-10 0:51 ` Andy Lutomirski
2014-06-10 2:57 ` Greg KH [this message]
2014-06-10 4:04 ` Andy Lutomirski
2014-06-10 4:14 ` Greg KH
2014-06-09 22:53 ` Linus Torvalds
2014-06-09 22:56 ` Andy Lutomirski
2014-06-09 23:36 ` Linus Torvalds
2014-06-10 12:50 ` Eric Paris
2014-06-10 15:42 ` Linus Torvalds
2014-06-10 15:48 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2014-05-28 22:21 [PATCH 0/2] Fix auditsc DoS and move it to staging Andy Lutomirski
2014-05-28 22:21 ` [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking Andy Lutomirski
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=20140610025715.GA24314@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=security@kernel.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox