[Top][All Lists]

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

Re: [Bug-gv] error opening files on other directories

From: Hans Fredrik Nordhaug
Subject: Re: [Bug-gv] error opening files on other directories
Date: Mon, 15 Nov 2004 11:54:15 +0100
User-agent: Mutt/1.4.1i

On Mon, Nov 15, 2004 at 01:38:50PM +0100, address@hidden wrote:
> So the problem is gs's "safe" option...

Yes, it seems so.

> It is possible to tell gs to accept non-trivial paths while remaining
> "safe"? Is the safe/unsafe state monolithic?

I think safer is monolithic. From the manual:

-dSAFER: Disables the deletefile and renamefile operators, and the ability to
open piped commands (%pipe%cmd) at all. Only %stdout and %stderr can be opened
for writing.  Disables reading of files other than %stdin, those given as a
command line argument, or those contained on one of the paths given by LIBPATH
and FONTPATH and specified by the system params /FontResourceDir and

jemarch wrote on https://savannah.gnu.org/bugs/?func=detailitem&item_id=10992:
> I would suggest to translate this discussion (and other bug related
> discussions) to address@hidden I think bug tracker follow-up comments should
> be used only in case of a change of the bug state.  Do you all agree?

I have seen the bug tracker follow-up been used for discussion on several
projects, but I don't mind using the mailing list - here I go:

Just some more comments:
> gs -dSAFER ../test/grfguide.pdf
is OK.
> ./gv ../test/grfguide.pdf
isn't OK, while
> ./gv ../test/grfguide.ps
is OK. (Assuming "safer" is set in gv of course.) Is there any difference in
how we treat pdf vs. ps files?

The problem with opening pdf files in gv (with newer version of ghostscript)
has been reported for several of the Linux distros, but no fixes posted.
Googling around did reveal any more info about this problem.


PS! jemarch: I sent a message to the list with wrong from address - just 
             delete it.

reply via email to

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