From: Leo Famulari <leo@famulari.name>
To: 22831@debbugs.gnu.org
Subject: bug#22831: [PATCH 2/2] WIP: gnu: openssl: Restrict allowed references for openssl.
Date: Tue, 1 Mar 2016 02:20:25 -0500 [thread overview]
Message-ID: <20160301072025.GA26797@jasmine> (raw)
In-Reply-To: <d59f912303428deb9ebbee6e3492edac988885f0.1456792742.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 160 bytes --]
On Mon, Feb 29, 2016 at 07:39:53PM -0500, Leo Famulari wrote:
> * gnu/packages/tls.scm (openssl)[arguments]: Add #:allowed-references.
Working patch attached.
[-- Attachment #2: 0001-gnu-openssl-Restrict-allowed-references-for-openssl.patch --]
[-- Type: text/x-diff, Size: 1312 bytes --]
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.
---
gnu/packages/tls.scm | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/gnu/packages/tls.scm b/gnu/packages/tls.scm
index 90971f2..8c72f3b 100644
--- a/gnu/packages/tls.scm
+++ b/gnu/packages/tls.scm
@@ -32,6 +32,7 @@
#:use-module (guix build-system python)
#:use-module (gnu packages compression)
#:use-module (gnu packages)
+ #:use-module (gnu packages gcc)
#:use-module (gnu packages guile)
#:use-module (gnu packages libffi)
#:use-module (gnu packages libidn)
@@ -200,6 +201,12 @@ required structures.")
`(#:parallel-build? #f
#:parallel-tests? #f
#:test-target "test"
+
+ ;; We want to limit what the output of this derivation refers to.
+ ;; Specifically, we don't want it to refer to Perl.
+ #:allowed-references ,(list (canonical-package glibc)
+ (list (canonical-package gcc) "lib")
+ "out")
#:phases
(modify-phases %standard-phases
(add-before
--
2.7.1
next prev parent reply other threads:[~2016-03-01 7:21 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 [this message]
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
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=20160301072025.GA26797@jasmine \
--to=leo@famulari.name \
--cc=22831@debbugs.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).