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:39:29 -0400 [thread overview]
Message-ID: <20180716173929.GA24955@jasmine.lan> (raw)
In-Reply-To: <20180716171430.GA20978@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On Mon, Jul 16, 2018 at 01:14:30PM -0400, Leo Famulari wrote:
> 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.
Dropbear's bundled libtomcrypt includes a variety of whitespace and
comment changes that make it non-trivial to compare the actual
differences between the codebases.
I'm not going to work on adapting the upstream patch for Dropbear, but
of course others are welcome to do it :) Otherwise I assume the Dropbear
team will include the fixes whenever they make a new release.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-16 17:40 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
2018-07-16 17:39 ` Leo Famulari [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180716173929.GA24955@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.