From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James Morris <jmorris@namei.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd fixes for 4.16
Date: Mon, 26 Feb 2018 11:49:06 -0800 [thread overview]
Message-ID: <1519674546.3941.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1802270552260.29062@namei.org>
On Tue, 2018-02-27 at 05:52 +1100, James Morris wrote:
> On Mon, 26 Feb 2018, Jarkko Sakkinen wrote:
>
> >
> > Hi
> >
> > Here is a batch of critical fixes for 4.16.
> >
>
> Do you have CVEs for these? If so, please include them in the commit
> messages.
Heh, well, I suppose from this everyone now knows they're fixes for
vulnerabilities. The CVE doesn't usually show up until after the
embargo is released, so we don't have one yet.
James
WARNING: multiple messages have this Message-ID (diff)
From: James.Bottomley@HansenPartnership.com (James Bottomley)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] tpmdd fixes for 4.16
Date: Mon, 26 Feb 2018 11:49:06 -0800 [thread overview]
Message-ID: <1519674546.3941.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1802270552260.29062@namei.org>
On Tue, 2018-02-27 at 05:52 +1100, James Morris wrote:
> On Mon, 26 Feb 2018, Jarkko Sakkinen wrote:
>
> >
> > Hi
> >
> > Here is a batch of critical fixes for 4.16.
> >
>
> Do you have CVEs for these???If so, please include them in the commit
> messages.
Heh, well, I suppose from this everyone now knows they're fixes for
vulnerabilities. ?The CVE doesn't usually show up until after the
embargo is released, so we don't have one yet.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James Morris <jmorris@namei.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd fixes for 4.16
Date: Mon, 26 Feb 2018 11:49:06 -0800 [thread overview]
Message-ID: <1519674546.3941.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1802270552260.29062@namei.org>
On Tue, 2018-02-27 at 05:52 +1100, James Morris wrote:
> On Mon, 26 Feb 2018, Jarkko Sakkinen wrote:
>
> >
> > Hi
> >
> > Here is a batch of critical fixes for 4.16.
> >
>
> Do you have CVEs for these? If so, please include them in the commit
> messages.
Heh, well, I suppose from this everyone now knows they're fixes for
vulnerabilities. The CVE doesn't usually show up until after the
embargo is released, so we don't have one yet.
James
next prev parent reply other threads:[~2018-02-26 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 12:41 [GIT PULL] tpmdd fixes for 4.16 Jarkko Sakkinen
2018-02-26 12:41 ` Jarkko Sakkinen
2018-02-26 18:52 ` James Morris
2018-02-26 18:52 ` James Morris
2018-02-26 19:49 ` James Bottomley [this message]
2018-02-26 19:49 ` James Bottomley
2018-02-26 19:49 ` James Bottomley
2018-02-26 23:33 ` James Morris
2018-02-26 23:33 ` James Morris
2018-02-26 23:33 ` James Morris
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=1519674546.3941.2.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 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.