Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID

To: debian-lts@lists.debian.org
Subject: Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID
From: Chris Lamb <lamby@debian.org>
Date: Mon, 28 Nov 2016 10:38:11 +0100
Message-id: <[🔎] 1480325891.2942907.800924745.2162646D@webmail.messagingengine.com>
In-reply-to: <[🔎] 20161128071326.jhvcaoavbkjpht4a@bogon.m.sigxcpu.org>
References: <[🔎] 20161128060237.GA26261@miami.connexer.com> <[🔎] 20161128071326.jhvcaoavbkjpht4a@bogon.m.sigxcpu.org>

Guido Günther wrote:

> If you're asking for code review posting a debdiff to the list might
> help people to pick it up.

Naive diffoscope output of the two .dscs:

  https://gist.github.com/lamby/70610714ff448db0be955c888ffaff06/raw



Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Reply to:

References:
- RFC - ImageMagick, proper testing, and handling issues without a CVE ID
  - From: Roberto C. Sánchez <roberto@connexer.com>
- Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID
  - From: Guido Günther <agx@sigxcpu.org>

Prev by Date: Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID
Next by Date: Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID
Previous by thread: Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID
Next by thread: Re: RFC - ImageMagick, proper testing, and handling issues without a CVE ID
Index(es):
- Date
- Thread