Re: Re: More Ghostscript Issues: Should we disable PS coders in policy.xml by default?

[Bob Friesenhahn <bfriesen () simple dallas tx us>]

On Thu, 23 Aug 2018, Leonardo Taccari wrote:
> (Regarding the `file.ps2' and `file.ps3' examples without `PS2:' or
> `PS3:' prefixes according `convert -debug Policy -log "%e"' it seems
> that they ends up as:
>
> Domain: Coder; rights=Read; pattern="PS" ...
>
> ...so should be blocked by the workaround described in
> VU#332928. But please correct me if I'm wrong.)

This is likely due to header magic detection (e.g. "%!PS-Adobe").  It 
is possible that a different path will be taken if the common 
Postscript header is not detected.  The file extension may then be 
used as a hint.  Also, there are a wide varieties of ImageMagick 
versions in use, with a wide variety of behaviors.

The version of ImageMagick provided by the Ubuntu Linux I am using at 
this moment dates from 2012!

Bob
--
Bob Friesenhahn
bfriesen () simple dallas tx us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/