bug-gv
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Nuno Silva
Subject: Re: [bug-gv] possible bug gv - won't open file
Date: Thu, 23 Feb 2017 18:31:42 +0200
User-agent: Mutt/1.5.24 (2015-08-30)

On 2017-02-23 10:18, M B wrote:
> Hello Mr Bader,
> 
> thanks for the clarification of the -dSAFER feature.
> 
> Is there a switch in a config file like ~/.profile or ~/.xinitrc that
> could be used for this purpose?

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 

If it does not take effect as soon as you change that file, you have to
run the command "xrdb --merge .Xresources".


(If you are starting gv from the commandline, there's also a --nosafer
option (so "gv --nosafer filename").)

> Alternatively, I do have root access on my home system and do not mind
> turning off the -dSAFER option by default somewhere you direct in the
> /etc directory.
> 
> Thanks to all in advance for the help.
> 
> Kind regards,
> 
> 
> 
> On 2/22/17, William Bader <address@hidden> wrote:
> > The file has the line
> >
> >   (georgia.ttf) (r) file dup run closefile
> >
> > By default, gv runs gs with -dSAFER to prevent running other files, since
> > that can create big security issues.
> >
> > It would be better to place the font in the gs font search path or to embed
> > the font in the file.
> >
> > If you really, really need to use the 'run' command and are willing to risk
> > the security issues, use 'State -> Ghostscript Options' and unselect the
> > 'Safer' button at the upper right.
> >
> > Regards,
> >
> > William
> >
> >
> > ________________________________
> > From: bug-gv on behalf of M B <address@hidden>
> > Sent: Wednesday, February 22, 2017 1:31 PM
> > To: address@hidden
> > Subject: [bug-gv] possible bug gv - won't open file
> >
> > Hello all,
> >
> > this email relates to a possible bug found in the debian 8 version of gv.
> >
> > The bug is in the file i/o section.
> >
> > A short test file (see attachment) malfunctions, while it is legal
> > PLRM syntax and has worked in all previous iterations of (debian)
> > Linux.
> >
> > The bug disappears in the ghostscript interpreter.
> >
> > Can anyone replicate the problem, and solve it?
> >
> > Thanks in advance
> >
> 

-- 
Nuno Silva



reply via email to

[Prev in Thread] Current Thread [Next in Thread]