Re: graphicsmagick update

2017-01-31 Thread Guido Günther
On Tue, Jan 31, 2017 at 04:07:19PM -0500, Antoine Beaupré wrote: > On 2017-01-31 21:42:41, Emilio Pozuelo Monfort wrote: > > I'd say it makes sense to release a regression update. > > > > BTW I'm not sure about this change, which is not mentioned in your > > changelog entry: > > > > ---

Re: graphicsmagick update

2017-01-31 Thread Antoine Beaupré
On 2017-01-31 21:42:41, Emilio Pozuelo Monfort wrote: > I'd say it makes sense to release a regression update. > > BTW I'm not sure about this change, which is not mentioned in your changelog > entry: > > --- graphicsmagick-1.3.16/debian/rules 2016-09-20 23:52:26.0 +0200 > +++

Re: graphicsmagick update

2017-01-31 Thread Emilio Pozuelo Monfort
On 16/01/17 20:48, Antoine Beaupré wrote: > Hi, > > I've looked at updating the graphicsmagick (GM) update to fix the issues > outlined in a [recent discussion][1]. The fix to CVE-2016-5240.patch is > trivial. I can also confirm the current GM version in wheezy-security > segfaults with the POC.

graphicsmagick update

2017-01-16 Thread Antoine Beaupré
Hi, I've looked at updating the graphicsmagick (GM) update to fix the issues outlined in a [recent discussion][1]. The fix to CVE-2016-5240.patch is trivial. I can also confirm the current GM version in wheezy-security segfaults with the POC. I've had difficulties fixing the pending