Thanks lot Yann for confirming.
regards,
Rashmi
On Sun, Jun 4, 2017 at 4:09 AM, Yann Ylavic wrote:
> Hi Rashmi,
>
> On Thu, Jun 1, 2017 at 11:19 AM, Rashmi Srinivasan
> wrote:
> > To port the fix for CVE-2016-8743 to 2.2.29, is
Hi Rashmi,
On Thu, Jun 1, 2017 at 11:19 AM, Rashmi Srinivasan
wrote:
> To port the fix for CVE-2016-8743 to 2.2.29, is it ok to port the
> changes from http://svn.apache.org/viewvc?view=revision=1777405
> Would that suffice?
> Please
Hi Yann,
Any update on this will be very helpful.
regards,
Rashmi
On Thu, Jun 1, 2017 at 2:49 PM, Rashmi Srinivasan <
rashmisrinivasan2...@gmail.com> wrote:
> Hi Yann,
> To port the fix for CVE-2016-8743 to 2.2.29, is it ok to port
> the changes from
Hi Yann,
To port the fix for CVE-2016-8743 to 2.2.29, is it ok to port the
changes from http://svn.apache.org/viewvc?view=revision=1777405
Would that suffice?
Please advise.
regards,
Rashmi
On Fri, Feb 10, 2017 at 1:30 PM, Rashmi Srinivasan <
Thank a lot for the patch Yann,
I will check if this fits in.
regards,
Rashmi
On Wed, Jan 25, 2017 at 6:04 PM, Yann Ylavic wrote:
> Hi,
>
> On Wed, Jan 25, 2017 at 9:17 AM, Rashmi Srinivasan
> wrote:
>
> > We are trying to port the fix
Hi,
On Wed, Jan 25, 2017 at 9:17 AM, Rashmi Srinivasan
wrote:
> We are trying to port the fix for CVE (CVE-2016-8743) to 2.4.18. Tried
> checking the revision on git for the list of files fixed for this CVE.
> There are lots of changes related to RFC7320 and
Hi,
We are trying to port the fix for CVE (CVE-2016-8743) to 2.4.18. Tried
checking the revision on git for the list of files fixed for this CVE.
There are lots of changes related to RFC7320 and was difficult to figure
out the files changed for this CVE as We couldnt find the CVE-2016-8743 in