emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#27263: closed (Perl CVE-2017-6512)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#27263: closed (Perl CVE-2017-6512)
Date: Wed, 07 Jun 2017 16:18:01 +0000

Your message dated Wed, 7 Jun 2017 12:17:53 -0400
with message-id <address@hidden>
and subject line Re: bug#27263: [PATCH 2/2] gnu: perl: Fix CVE-2017-6512 in 
File::Path.
has caused the debbugs.gnu.org bug report #27263,
regarding Perl CVE-2017-6512
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
27263: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27263
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Perl CVE-2017-6512 Date: Mon, 5 Jun 2017 23:01:08 -0400 User-agent: Mutt/1.8.3 (2017-05-23)
These patches fix CVE-2017-6512 in perl-file-path and the copy of
File::Path in perl itself.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#27263: [PATCH 2/2] gnu: perl: Fix CVE-2017-6512 in File::Path. Date: Wed, 7 Jun 2017 12:17:53 -0400 User-agent: Mutt/1.8.3 (2017-05-23)
On Wed, Jun 07, 2017 at 01:18:09AM +0200, Ludovic Courtès wrote:
> Leo Famulari <address@hidden> skribis:
> 
> > * gnu/packages/perl.scm (perl)[replacement]: New field.
> > (perl/fixed): New variable.
> > * gnu/packages/patches/perl-file-path-CVE-2017-6512.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> 
> OK too.
> 
> I suppose we’ll have to apply it in core-updates too, right?

And, done as c67d587f94173fd42d65097165afc5c512935646.

I tested that this packaging of Perl 5.26.0 builds on master, then I
"ported" the package to core-updates. I don't have the resources to
build the Perl package on core-updates in a timely manner.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]