Hi,
Didier LINK write:
Hi,
I see the point ... I will investigate before release (finally) a new GNU
GPL V3 version of ghostscript.
Thanks.
Below an updated link list regarding this bug and related bugs in
ghostscript:
[7]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584653
[8]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584663
[9]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584667
[1]http://bugs.ghostscript.com/show_bug.cgi?id=691339
[2]http://bugs.ghostscript.com/show_bug.cgi?id=691350
[3]http://www.securityfocus.com/archive/1/511433
[4]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583316
[5]https://bugzilla.novell.com/show_bug.cgi?id=608071
[6]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583183
and https://bugzilla.redhat.com/show_bug.cgi?id=599564
Bug 7 can be resolved by the attached patch (backported from Upstream revision
11352).
Bug 8 can be resolved by making "SEARCH_HERE_FIRST=0" the default (this is an option
to make (upstream)".
Bug 9 can be resolved by cherrypicking commit 11351 from upstream.
Please note that there are discussions making -dSAFER the default or not. No
solution for this available. If you decide to make -dSAFER the default, can you
send me the patch you needed for making that?
Thanks
Markus Steinborn
GNU gv maintainer