From: Vincent Legoll <vincent.legoll@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: GnuTLS security update
Date: Sun, 11 Sep 2016 18:08:27 +0200 [thread overview]
Message-ID: <CAEwRq=qLgtBJBZEdvuMjAQML4-ZB_-G6rf+rX5DUbKcJ6E-H7A@mail.gmail.com> (raw)
In-Reply-To: <20160911154108.GA13920@jasmine>
On Sun, Sep 11, 2016 at 5:41 PM, Leo Famulari <leo@famulari.name> wrote:
> 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.
Side questions (just for my curiosity's sake):
- What does it cost (manpower, hydra build time, etc...) approximatively
to do a new release ?
- Is it sufficiently automated ?
- Can we help ?
--
Vincent Legoll
next prev parent reply other threads:[~2016-09-11 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 15:41 GnuTLS security update Leo Famulari
2016-09-11 16:08 ` Vincent Legoll [this message]
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 21:37 ` bug#24418: " 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
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='CAEwRq=qLgtBJBZEdvuMjAQML4-ZB_-G6rf+rX5DUbKcJ6E-H7A@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).