|
BugTraq
vulnerabilities of postscript printers Jan 22 2004 06:45PM Bob Kryger (bobk panix com) (2 replies) Re: vulnerabilities of postscript printers Jan 23 2004 05:01AM Darren Reed (avalon caligula anu edu au) (6 replies) Re: vulnerabilities of postscript printers Jan 24 2004 02:56AM Glynn Clements (glynn clements virgin net) (1 replies) Re: vulnerabilities of postscript printers Jan 23 2004 07:21PM Elizabeth Zwicky (zwicky greatcircle com) (1 replies) Re: vulnerabilities of postscript printers Jan 23 2004 08:01PM Darren Reed (avalon caligula anu edu au) (1 replies) Re: vulnerabilities of postscript printers Jan 23 2004 06:40PM der Mouse (mouse Rodents Montreal QC CA) Re: vulnerabilities of postscript printers Jan 23 2004 04:15AM der Mouse (mouse Rodents Montreal QC CA) (2 replies) Re: vulnerabilities of postscript printers Jan 27 2004 10:12PM Ian Farquhar - Network Security Group (Ian Farquhar Sun COM) Re: vulnerabilities of postscript printers Jan 24 2004 12:41AM Michael Zimmermann (zim vegaa de) (1 replies) Re: vulnerabilities of postscript printers Jan 24 2004 04:38AM der Mouse (mouse Rodents Montreal QC CA) (1 replies) Re: vulnerabilities of postscript printers Jan 24 2004 09:39AM Michael Zimmermann (zim vegaa de) (1 replies) Re: vulnerabilities of postscript printers Jan 24 2004 05:26PM der Mouse (mouse Rodents Montreal QC CA) |
|
Privacy Statement |
> Btw, someone else mentioned something to the effect that hard drives
> were "new" to printers. Hard drives have been in printers for ~10 years
> (if not more) where you needed 100MB or so of space to spool print jobs.
Hard drives were available for the first of the Apple postscript
laser printers... In fact it was a standing joke that the
printers had more CPU power than the machines they were serving.
There were also a couple of postscript printers that had sun
workstations in their guts... They allowed telnet logins with
trivial (or no) root passwords.
----
I remember one case where someone had attached his PS printer
to a building wide (apartment) net. Didn't use DHCP so he just
assigned it a random address (that conflicted with available DHCP
allocations).
Somebody from the support group logged in to the printer,
did some investigation on it. The end solution was
to print a message on his printer asking him to call the
support group for help.
--
Stephen Samuel +1(604)876-0426 samuel (at) bcgreen (dot) com [email concealed]
http://www.bcgreen.com/~samuel/
Powerful committed communication. Transformation touching
the jewel within each person and bringing it to light.
[ reply ]