From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] perl: CVE-2016-2381
Date: Tue, 08 Mar 2016 17:59:00 -0000 [thread overview]
Message-ID: <87io0w4zrh.fsf@Rainer.invalid> (raw)
In-Reply-To: <87si029mqm.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 07 Mar 2016 19:17:05 +0100")
Achim Gratz writes:
> Yaakov Selkowitz writes:
>> A security vulnerability has been made public for perl:
>
> I've asked on p5p what the plan is for another 5.22 release. If that's
> too far off, I'll just patch 5.22.1, otherwise I'll wait for these
> patches (there are more fixes on the branch) to be released in 5.22.2.
The answer is that a release will happen "hoepfully before May", so
unless that shifts even further out I'd be inclined to wait for the
release.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2016-03-08 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 5:34 Yaakov Selkowitz
2016-03-07 18:17 ` Achim Gratz
2016-03-08 17:59 ` Achim Gratz [this message]
2016-03-08 18:32 ` Yaakov Selkowitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io0w4zrh.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/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.
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).