* Clark Taylor (2010-10-11) writes:
> I'm happy to be a guinea pig if you need.
A way to check if we are really dealing with a problem concerned with
the security features of Ghostscript would be to disable them and see if
the problem goes away. The following patch does this. It would be
interesting to see the results in your case.
Be sure to use this only if you are sure that the code in the generated
PostScript file is not malicious. And you should revert the changes in
preview.el again after testing, so that you don't leave a security hole
in your system.
--- preview.el.~1.284.~ 2009-06-18 21:20:46.000000000 +0200
+++ preview.el 2010-10-12 20:59:15.000000000 +0200
@@ -355,7 +355,7 @@
:group 'preview-gs
:type 'string)
-(defcustom preview-gs-options '("-q" "-dSAFER" "-dNOPAUSE"
+(defcustom preview-gs-options '("-q" "-dNOSAFER" "-dNOPAUSE"
"-DNOPLATFONTS" "-dPrinted"
"-dTextAlphaBits=4"
"-dGraphicsAlphaBits=4")
@@ -724,7 +724,7 @@
preview-gs-options
(nthcdr 2 image-info))
preview-gs-init-string
- (format "{DELAYSAFER{.setsafe}if}stopped pop\
+ (format "\
/.preview-BP currentpagedevice/BeginPage get dup \
null eq{pop{pop}bind}if def\
<</BeginPage{currentpagedevice/PageSize get dup 0 get 1 ne exch 1 get 1 ne or\
--
Ralf
_______________________________________________
bug-auctex mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-auctex
