2 ms·
The bloat in HP printer drivers has been well known for a long time, and I'm not surprised "telemetry" is now part of that. I stopped "upgrading" printers when
by userbinator 7y ago
The bloat in HP printer drivers has been well known for a long time, and I'm not surprised "telemetry" is now part of that. I stopped "upgrading" printers when they still used parallel ports and standard drivers the OS already had (no need to even touch the installation CD), so I don't know if the newer ones can also be used without installing the extra crap.
I imagine that a user’s data is exfiltrated back to HP by the printer itself, rather than any client-side software.
To me, that's a good reason (among others) to use a print server and plug the printer into it instead of a printer with its own networking; or if you must, keep it behind a firewall with no access to the Internet. Although I have no interest in owning one, I'd be curious to packet-sniff one of these.
- reaperducer 7y agoTo me, that's a good reason (among others) to use a print server and plug the printer into it instead of a printer with its own networking That's an excellent idea. I wish I'd thought of it. I have a couple of old Airport Expresses lying around with USB ports on them. I wonder if one of them could be pressed into service in this manner.
- NegativeLatency 7y agoI did this, just needed to torrent and install an old version of 10.6 on a VM so I could configure the airport. Raspberry pis also make decent print servers
- javajosh 7y agoAnother option is to a) give your printer a static IP (or setup DHCP to assign it's MAC a consistent IP) and b) add a routing rule to not forward packets from that IP. (However, a print server is strictly better if only because you just can't know what such a printer is going to do on your network!)