From: "Sudler, Simon" <simon.sudler@siemens.com>
To: "libc-stable@sourceware.org" <libc-stable@sourceware.org>
Subject: BZ #21361 backport to version prior 2.26?
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <EB4794275C0C904BBABD6840AB8DC22D059208E2@DENBGAT9EL2MSX.ww902.siemens.net> (raw)
Hello,
Sorry for the wrong subject last time:
I noticed, that the #21361 (CVE-2017-12132) issue was fixed for 2.26, but was not applied in the any older release branches. The patch applies perfectly for the code with the vulnerability, only the tests requires some backporting.
Is there any reason why this issue has not been fixed in any older release?
With best regards,
Simon Sudler
Siemens AG
Process Industries and Drives Division
Process Automation
www.siemens.com/ingenuityforlife
Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Joe Kaeser, Chairman, President and Chief Executive Officer; Roland Busch, Lisa Davis, Klaus Helmrich, Janina Kugel, Cedrik Neike, Michael Sen, Ralf P. Thomas; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
next reply other threads:[~2017-11-13 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 Sudler, Simon [this message]
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 + Sudler, Simon
2017-01-01 0:00 ` BZ #21361 backport to version prior 2.26? Was: + Tulio Magno Quites Machado Filho
2017-01-01 0:00 ` AW: " Sudler, Simon
2017-01-01 0:00 ` BZ #21361 backport to version prior 2.26? Florian Weimer
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=EB4794275C0C904BBABD6840AB8DC22D059208E2@DENBGAT9EL2MSX.ww902.siemens.net \
--to=simon.sudler@siemens.com \
--cc=libc-stable@sourceware.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.
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).