Re: [bug-gv] possible bug gv - won't open file

[M B]

Hello all,

thanks to all who replied about the "-dSAFER" feature, and how to defeat it.

It turns out that command-line switch "--nosafer" also works.

Attached are screenshot png images from my computer which detail the
behaviour of gv under various conditions.  The last attachment is the
file "test.ps".

Figure 1 shows the "standard" -dSAFER behaviour.

Figure 2 shows the "--nosafer" behaviour. "georgia.ttf" cannot be
found, but it is located in the CWD.  Note the difference in error
message content between Fig 1 and Fig 2.

Figure 3 shows the "--nosafer" behaviour with the PWD pre-pended to
the filename. Surprisingly, this works as expected.

Figure 4 shows the "--nosafer" behaviour with filename "./georgia.ttf"
as argument. It fails, just as in Fig 2.

I would argue that Figs 2 and 4 ought to be similar to Fig 3, and that
the behaviour is not a feature.

Thanks to any and all for the help.






On 2/23/17, Markus Steinborn <address@hidden> wrote:
> Hello,
>
> Nuno Silva wrote:
>> Hello,
>>
>>  From what I can see, gv seems to have a gsSafer resource, so you can try
>> adding
>>
>>      gv.gsSafer: False
>>
>> to $HOME/.Xresources or $HOME/.Xdefaults
>>
> Or add that line to an existing ~/.gv (can be created by saving settings
> either in GV options or ghostscript options.
>
> Greetings
>
> Markus Steinborn
> GNU gv maintainer
>
>

gvscreenshot.png
Description: PNG image

gvnosafer.png
Description: PNG image

gvpwd.png
Description: PNG image

gvdot.png
Description: PNG image

test.ps
Description: PostScript document