From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: OpenSSL CVE-2016-2177, CVE-2016-2178
Date: Sat, 11 Jun 2016 21:22:01 -0400 [thread overview]
Message-ID: <20160612012201.GA23504@jasmine> (raw)
Some bugs in OpenSSL were recently disclosed.
CVE-2016-2177
http://seclists.org/oss-sec/2016/q2/500
CVE-2016-2178
http://seclists.org/oss-sec/2016/q2/493
The second bug can apparently be used by an attacker to recover DSA
keys. And remember that OpenSSH uses OpenSSL, so it is affected too.
Should we try cherry-picking the upstream commits from the OpenSSL
development repo?
next reply other threads:[~2016-06-12 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 1:22 Leo Famulari [this message]
2016-06-12 20:49 ` OpenSSL CVE-2016-2177, CVE-2016-2178 Ludovic Courtès
2016-06-13 20:27 ` Leo Famulari
2016-06-14 12:13 ` Ludovic Courtès
2016-06-15 14:59 ` 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=20160612012201.GA23504@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.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.
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).