Re:Attacking Unix Systems via Cups, Part I
by mikepavone on Thursday September 26, 2024 @05:27PM
(#41663591)
cupsd is configured to listen locally, but cups-browsed has to listen on the network to do its job (network printer auto-discovery)
[ Parent
| on HN ]
Re:Attacking Unix Systems via Cups, Part I
by gordonfish on Thursday September 26, 2024 @06:50PM
(#41664392)
> but cups-browsed has to listen on the network to do its job (network printer auto-discovery)
Isn't listening on 0.0.0.0 instead of localhost only needed if the machine itself is hosting a printer that needs to be accessible to other hosts?
Re:Attacking Unix Systems via Cups, Part I
by mikepavone on Thursday September 26, 2024 @08:32PM
(#41665073)
I am very unfamiliar with the protocol, but my impression from a little reading is that the sharing computer broadcasts and the receiver listens. This appears to be for some CUPS specific browsing/discovery protocol rather than mDNS/DNS-SD (cups-browsed supports adding printers discovered that way but depends on avahi to handle the mDNS part).
EDIT: Here's a description of the protocol in question: https://opensource.apple.com/source/cups/cups-327/cups/doc/h...
Re:Attacking Unix Systems via Cups, Part I
by tsimionescu on Friday September 27, 2024 @01:50AM
(#41666675)
No, per the article, cups-browsed is used so that a printer can register itself to your system. The printer is the one that initiates a connection to tell your system that it is available at some URL.