Dear Chris,
I now see what tripped me up: in my Packages file, printconf depends on
ghostscript, but foomatic-filters doesn't. Maybe that could be fixed?
Thanks, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sy
Processing commands for cont...@bugs.debian.org:
> reopen 584026
Bug #584026 {Done: Chris Lawrence } [printconf] printconf:
Security bugs in ghostscript
> reassign 584026 foomatic-filters
Bug #584026 [printconf] printconf: Security bugs in ghostscript
Bug reassigned from package 'printconf' to 'f
reopen 584026
reassign 584026 foomatic-filters
thanks
Dear Chris,
> ... doesn't apply to printconf. foomatic-filters is the only
> Foomatic-related package that is affected by calling gs directly,
> and I assume your mass-filed bug reports have hit that one too.
Sorry, no. Seems my "pick out p
On Mon, May 31, 2010 at 10:47 PM, wrote:
> Regardless, this bug (#584026: printconf) is hardly "done".
Yes, it is, because it doesn't apply to printconf. foomatic-filters
is the only Foomatic-related package that is affected by calling gs
directly, and I assume your mass-filed bug reports have
Package: printconf
Severity: grave
Tags: security
Justification: user security hole
Please note remote execute-any-code security bugs in ghostscript:
http://bugs.debian.org/583183
This package depends on ghostscript, and may be affected. Please
evaluate the security of this package, and fix i
5 matches
Mail list logo