From: Leo Famulari <leo@famulari.name>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 31831@debbugs.gnu.org
Subject: bug#31831: CVE-2018-0495 Key Extraction Side Channel in Multiple Crypto Libraries
Date: Mon, 16 Jul 2018 13:14:30 -0400 [thread overview]
Message-ID: <20180716171430.GA20978@jasmine.lan> (raw)
In-Reply-To: <CAE4v=pi3GY239AEQYS4MmYgjBo-kHoA3+gx5TN009fcR_gmneQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
On Mon, Jul 16, 2018 at 08:53:56AM +0200, Gábor Boskovits wrote:
> Are there any more packages needing attention?
libtomcrypt version 1.18.2 includes a fix; we would need to adapt this
to the bundled copy in Dropbear. I can take a look at this today.
NSS was fixed in Guix commit 7c3bea7e6299e1026c7964c83986a6b6c220879a by
Marius. Thanks, Marius!
The advisory mentions similar but not indentical issues in these
packages:
There is a new release of Crypto++ available. I'm not sure if this
addresses whatever issue was mentioned in the original advisory.
mbedTLS's changelog doesn't mention anything related to key extraction
side channels.
I don't see any related commits in Go's crypto/tls Git repo.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-16 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 19:22 bug#31831: CVE-2018-0495 Key Extraction Side Channel in Multiple Crypto Libraries Leo Famulari
2018-06-14 19:50 ` Leo Famulari
2018-06-14 19:53 ` Gábor Boskovits
2018-06-14 20:06 ` Leo Famulari
2018-06-14 20:44 ` Gábor Boskovits
2018-06-14 20:45 ` Leo Famulari
2018-06-18 16:35 ` Leo Famulari
2018-07-16 6:20 ` Leo Famulari
2018-07-16 6:53 ` Gábor Boskovits
2018-07-16 17:14 ` Leo Famulari [this message]
2018-07-16 17:39 ` Leo Famulari
2019-02-26 2:01 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180716171430.GA20978@jasmine.lan \
--to=leo@famulari.name \
--cc=31831@debbugs.gnu.org \
--cc=boskovits@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).