[gs-bugs] [Bug 691955] Missing CIDFmap?

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon Feb 14 09:25:36 UTC 2011


--- Comment #7 from Ken Sharp <ken.sharp at artifex.com> 2011-02-14 09:25:34 UTC ---
(In reply to comment #6)

> It seems that my problem is mainly caused by "-dPARANOIDSAFER". 

Yes, this seems to be the case.

> ----------------------------------------
> Case 1 :without using "-dPARANOIDSAFER"
> ----------------------------------------
> I think that the generated ps file is not converted successfully (correctly)
> because it can be viewed by other tools properly. 

Sorry, you're still losing me here. If you don't use -dPARANOIDSAFER I thought
that Ghostscript was correctly finding the font and rendering the file. Is this
not the case ?

> ----------------------------------------
> Case 2 :with using "-dPARANOIDSAFER"
> ----------------------------------------
> In the same Solaris 10, I still keep the old GS 8.1.5. When I use the same GS
> command to run, it can generate and view the ps without any problem. I think
> that there is something is wrong in the new version GS9.00.

The action of SAFER and PARANOIDSAFER was modified recently (in version 9.00)
because of security concerns raised by various Unix users.  

If I remember correctly there was quite an involved discussion around this at
the time, as we felt that changing the behaviour would confuse users, but the
concerned users felt the security benefits outweighed this.

This difference in behaviour is presumably causing your problem.

> At this moment, I
> don't want force back to use the old version because the new Gs9.00 is compiled
> with cups-1.4.6. On my previous reply (on 2011-02-14 08:12:23 UTC), the log (as
> below) shows that gs cannot load that font.

This produces the 'invalidfileaccess error, which should be resolved if you
remove the -dPARANOIDSAFER switch.

> However, in gs prompt, it can load
> it successfully. As I mentioned I logon as "root", I should have all necessary
> privillege.

PARANOIDSAFER does not consult user privileges, it completely disables certain
kinds of file access from the PostScript environment. If you activate this
switch certain file accesses are *totally* disabled, no matter what the current
user is.

> From the directory list(last email), it shows the font file is 644
> (everyone can read/access). Therefore, what's the problem???  

See above, access permissions are not relevant to this switch.

Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the gs-bugs mailing list