bugtraq - Re: vulnerabilities of postscript printers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <v04210102bc3722fd9c95@[10.0.1.2]>
Date: Fri, 23 Jan 2004 11:21:52 -0800
From: Elizabeth Zwicky <zwicky@...atcircle.com>
To: Darren Reed <avalon@...igula.anu.edu.au>
Cc: bugtraq@...urityfocus.com
Subject: Re: vulnerabilities of postscript printers

> 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.

Sure there is. PostScript has all the standard file handling, among
other things for handling peripherals for font storage. Alas, I am
moving at the moment and don't have my PostScript manuals to hand,
but, for instance, I've written code that used PostScript filehandling
in GhostScript to modify files in a user's home directory, and code that
used the hard drive in a printer that had one for font caching. In general,
PostScript printers use PostScript as their underlying OS. It is
quite certainly a full programming language.

>Of course if you had a postscript printer AND a the postscript cookbooks
>you'd instantly get a better understanding.

Umm, apparently not. Although the PostScript manuals are handy, you
need to dig pretty deep into them to get to relatively little-used
commands.

	Elizabeth Zwicky
	zwicky@...atcircle.com