[33232] in bugtraq
Re: vulnerabilities of postscript printers
daemon@ATHENA.MIT.EDU (der Mouse)
Sat Jan 24 14:30:57 2004
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200401231849.NAA07896@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Date: Fri, 23 Jan 2004 13:40:17 -0500 (EST)
To: Darren Reed <avalon@caligula.anu.edu.au>, bugtraq@securityfocus.com
In-Reply-To: <200401230501.i0N5120i017266@caligula.anu.edu.au>
> I've never heard of anyone suggesting you could copy data from one
> port to another, if only because there's no such thing as an open
> file in postscript.
Actually, PostScript does have open files; find a Red Book, look up the
"file" operator, and follow the pointers to elsewhere. (Many/most
PostScript-capable devices do not have anything of significance by way
of a filesystem, but that's a different issue entirely.)
> Of course if you had a postscript printer AND a the postscript
> cookbooks you'd instantly get a better understanding.
And if you actually read the Red Book, _you_'d get a better
understanding. In the Second Edition Red Book, for example, you'd want
to read section 3.8, "File Input and Output".
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse@rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
