From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: GnuTLS security update
Date: Sun, 11 Sep 2016 11:41:08 -0400 [thread overview]
Message-ID: <20160911154108.GA13920@jasmine> (raw)
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
There is a GnuTLS security advisory [0] regarding "an issue that affects
validation of certificates using OCSP responses, which can falsely
report a certificate as valid under certain circumstances."
I updated GnuTLS on core-updates to 3.5.4, the latest release of the 3.5
series.
For master, the naive approach of cherry-picking the patch [1] did not
work; the test 'system-prio-file' fails consistently with that change. I
could instead try grafting the updated version.
What do you think? The authors seem to think it's a relatively minor
issue [2], since exploiting it requires an attacker to compromise the
certificate authority.
[0]
http://gnutls.org/security.html#GNUTLS-SA-2016-3
http://lists.gnutls.org/pipermail/gnutls-devel/2016-September/008146.html
[1]
https://gitlab.com/gnutls/gnutls/commit/964632f37dfdfb914ebc5e49db4fa29af35b1de9
[2]
http://lists.gnutls.org/pipermail/gnutls-devel/2016-September/008148.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-09-11 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 15:41 Leo Famulari [this message]
2016-09-11 16:08 ` GnuTLS security update Vincent Legoll
2016-09-11 20:45 ` Ludovic Courtès
2016-09-11 20:54 ` Ludovic Courtès
2016-09-12 1:53 ` Leo Famulari
2016-09-12 3:28 ` Leo Famulari
2016-09-12 12:56 ` Ludovic Courtès
2016-09-12 16:34 ` Leo Famulari
2016-10-14 7:57 ` bug#24418: Grafted item refers to a mixture of grafted and ungrafted outputs of the same derivation Ludovic Courtès
2016-10-14 21:37 ` bug#24418: GnuTLS security update Ludovic Courtès
2016-10-14 21:37 ` Ludovic Courtès
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=20160911154108.GA13920@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 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.