bugGNU gv - Bugs: bug #10992, ../paths cannot be read

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #10992: ../paths cannot be read

Submitter:  Karl Berry <karl>
Submitted:  Sun 14 Nov 2004 02:00:29 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  jemarch
Open/Closed:  Closed Release:  None

Jump to the original submission

Mon 15 Nov 2004 01:46:04 PM UTC, comment #8: 

Bug fixed.

Jose E. Marchesi <jemarch>
Mon 15 Nov 2004 10:17:25 AM UTC, comment #7: 

I would suggest to translate this discussion (and other bug related discussions) to -email is unavailable-

I think bug tracker follow-up comments should be used only in case of a change of the bug state.

Do you all agree?

Jose E. Marchesi <jemarch>
Mon 15 Nov 2004 09:45:30 AM UTC, comment #6: 

Sorry, you are correct - this has nothing to do with pdf2dsc. It's the "safer" setting. Unsetting "safer" (which we really don't want) works. Using full paths doesn't help - you must cd to the directory containing the file. Even using the open file dialog doesn't help...

Hans Fredrik Nordhaug <hansfn>
Mon 15 Nov 2004 09:11:44 AM UTC, comment #5: 

The pdf2dsc bug is unrelated: it is already solved on CVS gv.

GNU gv do not actually call pdf2dsc at all but call gs directly.

If your gv is calling pdf2dsc it is because it is reading the resources file /etc/X11/app-defaults/GV (or /usr/X11R6/lib/app-defaults) shipped with another gv version (Debian or RedHat one, for example).

Now GNU gv installs the resource file GV into $(pkglib)/GV, and the bug was fixed.

So the paths problem is due to another reason...

Jose E. Marchesi <jemarch>
Mon 15 Nov 2004 08:57:34 AM UTC, comment #4: 

OK, I can reproduce it, but it's not related to ".." in paths, but to pdf files (only).



>./gv grfguide.pdf

Error: /undefinedfilename in --file--
Operand stack:
   PDFfile   (0x80bf660df)   (r)
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1116/1686(ro)(G)--   --dict:0/20(G)--   --dict:70/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 1914
GPL Ghostscript 8.15: Unrecoverable error, exit code 1




Doesn't happen with ps files. (This happens with both gs 8.14 and 8.15.)

The actual problem is "pdf2dsc %pdf %dsc". It seems what is inserted is "0x80bf660df" instead of the filename "grfguide.pdf". (Try "pdf2dsc grfguide.pdf grfguide.dsc" from the command line - works with no problems.) Now it should be easier to track down :-)

(I used grfguide.ps comming with teTeX and converted it to grfguide.pdf with ps2pdf - if we should test with the same file.)

Hans Fredrik Nordhaug <hansfn>
Mon 15 Nov 2004 08:43:27 AM UTC, comment #3: 

Doesn't happen with AFPL gs 8.14 or GPL gs 8.15 for me. I have made no changes to gs 8.15 (and I'm running gv with safer enabled).

Hans Fredrik Nordhaug <hansfn>
Mon 15 Nov 2004 07:09:50 AM UTC, comment #2: 

Happens with GPL gs 8.15. Do not happens with GNU gs 7.05.

New security policies regarding file paths? (.. in a path is forbidden).

Try to work with full paths.

Jose E. Marchesi <jemarch>
Sun 14 Nov 2004 11:22:32 PM UTC, comment #1: 

I am unable to reproduce this bug.

Could you please give me more detailed information? This happens with all ../directory/file?

Jose E. Marchesi <jemarch>
Sun 14 Nov 2004 02:00:29 PM UTC, original submission:  

gv ../somedir/somefile gets an error from Ghostscript:

Error: /invalidfileaccess in --file--

I don't know if anything can be done, but I thought I'd mention it.

Karl Berry <karl>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follow 7 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2004-11-15 jemarch StatusNone Fixed
    Open/ClosedOpen Closed
2004-11-15 jemarch Summarypdf2dsc fails on filename ../paths cannot be read
2004-11-15 hansfn Summary../paths cannot be read pdf2dsc fails on filename
2004-11-15 jemarch StatusWorks For Me None
2004-11-14 jemarch Assigned toNone jemarch
2004-11-14 jemarch StatusNone Works For Me

Back to the top

Powered by Savane 3.13-758e.
Corresponding source code