Windows 0day privilege escalation still not fixed

Re:Windows 0day privilege escalation still not fixed by rbanffy on Thursday December 24, 2020 @10:28AM (#25528275)

Printing was complicated in those days because a computer couldn't hold a bitmap of a printed page in memory and still do anything. Early PostScript printers were also much more powerful than the PCs that drove them, often with 32 bit RISC CPUs, dozens of megabytes of RAM and some even had SCSI disks.

Now that most computers can hold a page in their L2 caches, it's easy and much faster to render in-memory and send a bitmap over to the printer driver to let it print with whatever options it wants. All the driver needs is to accept a bitmap and print it as well as it can and you can safely ignore most of the printer's own PDL.

Most of the thorny issues in printing are with special-purpose printers - thermal, barcode, embedded text only, etc.

Apple uses CUPS and it should work fine with older printers. Last time I checked, CUPS could handle an HP Deskjet 500 (if you have the parallel port)

[ Parent | on HN ]

Re:Windows 0day privilege escalation still not fixed by tubs on Thursday December 24, 2020 @07:39PM (#25533069)

Fun story I heard from an aerospace engineer - they were running some heavy simulations and producing graphs.

He found the printer that was emitting the graphs was actually more powerful than the (very expensive) machines running the simulations, to the point that converting the simulation to postscript (or some variant thereof) and running it directly on the printer was some orders of magnitude faster.

[ Parent | on HN ]

Re:Windows 0day privilege escalation still not fixed by rbanffy on Friday December 25, 2020 @05:51AM (#25535694)

Indeed. I've seen printers churn out beautiful fractals at a fraction of the time it took 68K Macs to do it.

[ Parent | on HN ]