News for hackers. Stuff that matters.

A comment on Remote Code Execution in ImageMagick (CVE-2016–3714).

Re:Remote Code Execution in ImageMagick (CVE-2016–3714) by michaelmcmillan on Tuesday May 03, 2016 @03:22PM (#11623462)
https://github.com/ImageMagick/ImageMagick/commit/e93e339c0a...
[ Parent | on HN ]
Re:Remote Code Execution in ImageMagick (CVE-2016–3714) by oneweekwonder on Tuesday May 03, 2016 @03:33PM (#11623529)
Any insight?
[ Parent | on HN ]
Re:Remote Code Execution in ImageMagick (CVE-2016–3714) by alxndr on Tuesday May 03, 2016 @03:55PM (#11623689)
No insight, but the diff is easier to look at if you tell GitHub to ignore (most) whitespace with `?w=1`: https://github.com/ImageMagick/ImageMagick/commit/e93e339c?w...
[ Parent | on HN ]
Re:Remote Code Execution in ImageMagick (CVE-2016–3714) by bpicolo on Tuesday May 03, 2016 @04:28PM (#11623960)
That diff seems logicless
[ Parent | on HN ]
Re:Remote Code Execution in ImageMagick (CVE-2016–3714) by alxndr on Tuesday May 03, 2016 @04:38PM (#11624033)
With a commit message like "whitespace cleanup" I would expect the diff to look something like that.

I like to have GitHub show the diff with whitespace ignored as it's then easier to verify that no other code changes snuck in to the commit(s).

[ Parent | on HN ]