Re: Wheezy update of trafficserver?
For the record, I have marked this as "not-affected" in the security
tracker. During my tests in April, I wasn't able to reproduce the issue
in a Wheezy virtual machine. Furthermore, the fix is very intrusive and
would be quite difficult to backport.
A.
On 2017-04-26 12:23:16, Antoine Beaupre wrote:
> Dear maintainer(s),
>
> The Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of trafficserver:
>
> https://security-tracker.debian.org/tracker/CVE-2017-5659
>
> Would you like to take care of this yourself?
>
> If yes, please follow the workflow we have defined here:
>
> https://wiki.debian.org/LTS/Development
>
> If that workflow is a burden to you, feel free to just prepare an
> updated source package and send it to debian-lts@lists.debian.org
> (via a debdiff, or with an URL pointing to the source package,
> or even with a pointer to your packaging repository), and the members
> of the LTS team will take care of the rest. Indicate clearly whether you
> have tested the updated package or not.
>
> If you don't want to take care of this update, it's not a problem, we
> will do our best with your package. Just let us know whether you would
> like to review and/or test the updated package before it gets released.
>
> You can also opt-out from receiving future similar emails in your
> answer and then the LTS Team will take care of trafficserver updates
> for the LTS releases.
>
> Thank you very much.
>
> Antoine Beaupré,
> on behalf of the Debian LTS team.
>
> PS: A member of the LTS team might start working on this update at
> any point in time. You can verify whether someone is registered
> on this update in this file:
>
> https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
> --
--
Every one of us is, in the cosmic perspective, precious. If a human
disagrees with you, let him live. In a hundred billion galaxies, you
will not find another. - Carl Sagan
Reply to: