From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Adding packages with vulnerabilities (was Re: [PATCH 1/2] gnu: Add perl-net-psyc. [pcre])
Date: Mon, 03 Oct 2016 17:44:04 +0200 [thread overview]
Message-ID: <87twcta14r.fsf@gnu.org> (raw)
In-Reply-To: <20161002015022.GB26660@jasmine> (Leo Famulari's message of "Sat, 1 Oct 2016 21:50:22 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Thu, Sep 29, 2016 at 08:58:29AM +0000, ng0 wrote:
>> Leo Famulari <leo@famulari.name> writes:
>> > On Wed, Sep 21, 2016 at 06:46:31PM +0000, ng0 wrote:
>> >> Subject: [PATCH 1/2] gnu: Add psyclpc.
>> >>
>> >> * gnu/packages/psyc.scm (psyclpc): New variable.
>
>> >> + (inputs
>> >> + `(("zlib" ,zlib)
>> >> + ("openssl" ,openssl)))
>> >> + ;; pcre is bundled to ensure the version is compatible. XXX: look into
>> >> + ;; unbundling it. Upstream should update from pcre 4.5 to 8.38. For
>> >> + ;; functionality reasons we can not unbundle it now.
>> >> + ;; ("pcre" ,pcre)))
>> >
>> > That version of PCRE was released in 2003. We might want to add a
>> > warning to the package description...
>> >
>> > https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre
>>
>> Update on this: the pcre bundling was inherited from ldmud, current
>> ldmud has unbundled pcre, so we will be able to unbundle pcre.
>>
>> I'd still like to have the patches in their current form and update
>> psyclpc when the next version without pcre is out.
>
> I'd like some more opinions on this. Should we add this package even
> though we know it contains some security bugs (linked above)?
I don’t think so.
From the comment above, it seems difficult to have this package use a
current version of PCRE, right? Then I would suggest discussing it with
upstream. After all, they’re developing network-facing software, so
they’re probably interested in avoiding security issues.
ng0, could you take it with them?
TIA,
Ludo’.
next prev parent reply other threads:[~2016-10-03 15:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 11:32 [PATCH 1/2] gnu: Add perl-net-psyc ng0
2016-09-13 11:32 ` [PATCH 2/2] gnu: Add libpsyc ng0
2016-09-13 19:17 ` Leo Famulari
2016-09-13 19:16 ` [PATCH 1/2] gnu: Add perl-net-psyc Leo Famulari
2016-09-13 19:34 ` ng0
2016-09-13 20:55 ` ng0
2016-09-21 9:17 ` ng0
2016-09-21 10:34 ` ng0
2016-09-21 18:46 ` ng0
2016-09-27 16:56 ` Leo Famulari
2016-09-27 21:41 ` ng0
2016-09-28 14:03 ` ng0
2016-09-29 8:58 ` [PATCH 1/2] gnu: Add perl-net-psyc. [pcre] ng0
2016-10-02 1:50 ` Adding packages with vulnerabilities (was Re: [PATCH 1/2] gnu: Add perl-net-psyc. [pcre]) Leo Famulari
2016-10-02 10:30 ` ng0
2016-10-02 10:40 ` ng0
2016-10-03 15:44 ` Ludovic Courtès [this message]
2016-10-03 21:06 ` ng0
2016-09-27 16:49 ` [PATCH 1/2] gnu: Add perl-net-psyc Leo Famulari
2016-09-28 15:47 ` [PATCH] Add psyc* suite ng0
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=87twcta14r.fsf@gnu.org \
--to=ludo@gnu.org \
--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).