From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 22831@debbugs.gnu.org
Subject: bug#22831: [PATCH 2/2] WIP: gnu: openssl: Restrict allowed references for openssl.
Date: Wed, 02 Mar 2016 21:59:25 +0100 [thread overview]
Message-ID: <87wppkeguq.fsf@gnu.org> (raw)
In-Reply-To: <20160302192022.GD15618@jasmine> (Leo Famulari's message of "Wed, 2 Mar 2016 14:20:22 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Mar 02, 2016 at 09:42:41AM +0100, Ludovic Courtès wrote:
>> Leo Famulari <leo@famulari.name> skribis:
>>
>> > On Tue, Mar 01, 2016 at 09:46:26PM +0100, Ludovic Courtès wrote:
>> >> Leo Famulari <leo@famulari.name> skribis:
>> >>
>> >> > From 00807e4421757f8d9204f1601de9a8286a408f91 Mon Sep 17 00:00:00 2001
>> >> > From: Leo Famulari <leo@famulari.name>
>> >> > Date: Mon, 29 Feb 2016 19:24:20 -0500
>> >> > Subject: [PATCH] gnu: openssl: Restrict allowed references for openssl.
>> >> >
>> >> > * gnu/packages/tls.scm (openssl)[arguments]: Add #:allowed-references.
>> >>
>> >> For some reason I hadn’t seen it in M-x debbugs-gnu for this report
>> >> today, but the patch looks good to me!
>> >>
>> >> If we apply it now, it won’t trigger a rebuild (yay!), but will still
>> >> trigger a bunch of regrafting, which is slightly annoying. What about
>> >> applying it in the next ‘security-updates’ branch?
>> >
>> > Sure. Is it okay if I create that branch?
>>
>> Sure, no problem.
>
> Since there was already a security-updates job started, how about
> putting on core-updates?
Dunno, what does Mark think? Let’s check with Mark on IRC. :-)
Ludo’.
next prev parent reply other threads:[~2016-03-02 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 17:05 bug#22831: OpenSSL should not depend on Perl Ludovic Courtès
2016-02-28 1:10 ` Leo Famulari
2016-02-28 13:35 ` Ludovic Courtès
2016-02-29 8:47 ` Leo Famulari
2016-03-01 13:38 ` Ludovic Courtès
2016-03-01 17:24 ` Ludovic Courtès
2016-02-28 13:37 ` Ludovic Courtès
2016-02-29 8:48 ` Leo Famulari
2016-03-01 0:39 ` bug#22831: [PATCH 0/2] OpenSSL / Perl run-time dependency Leo Famulari
2016-03-01 0:39 ` bug#22831: [PATCH 1/2] gnu: openssl: Remove run-time dependency on Perl Leo Famulari
2016-03-01 0:39 ` bug#22831: [PATCH 2/2] WIP: gnu: openssl: Restrict allowed references for openssl Leo Famulari
2016-03-01 7:18 ` Leo Famulari
2016-03-01 7:20 ` Leo Famulari
2016-03-01 20:46 ` Ludovic Courtès
2016-03-01 21:04 ` Leo Famulari
2016-03-02 8:42 ` Ludovic Courtès
2016-03-02 19:20 ` Leo Famulari
2016-03-02 20:59 ` Ludovic Courtès [this message]
2016-03-21 2:20 ` bug#22831: [PATCH 0/1] Disallow reference to Perl from OpenSSL Leo Famulari
2016-03-21 2:20 ` bug#22831: [PATCH 1/1] gnu: openssl: Enforce non-reference to perl Leo Famulari
2016-03-21 9:29 ` Ludovic Courtès
2016-03-21 16:23 ` 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=87wppkeguq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22831@debbugs.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).