2 ms·
Two downsides to being able to send PDF bytes direct to TCP port 9100 hosted directly by the printer firmware on the printer's own network interface... * That'
by neilv 5y ago
Two downsides to being able to send PDF bytes direct to TCP port 9100 hosted directly by the printer firmware on the printer's own network interface...
* That's not encrypted.
* (More importantly) You might look at the printer firmware's complexity, excessive IoT/cloud-friendliness, and hints from the printer brand about their current engineering standards... and become uneasy about plugging that into your LAN, even if you firewall it to heck.
Partial solution: for my modern laser printer, I've left its NIC unconnected, and put my own print server in front of it, on a VLAN, and connected via USB. And I still strongly suspect at least a couple classes of vulnerability still present, but no time to look into it or mitigate.
Variation for the article's needs: you can make a one-line script TLS/SSL tunnel from a local port on your workstation host(s), to a thin isolating host (old RasPi?) in front of the printer. So content is encrypted over the LAN, and the printer is more isolated than it would be normally.
Another variation: plug the printer directly into a single host that needs it (such as via USB or a dedicated Ethernet NIC), and then decide what to do about any other hosts that want to use the printer.