You are viewing a single thread.
View all comments 5 points
I have cups (but not cups-browsed) installed, but I only start the service when I need to print something a few times a year. Until then it is only a binary sitting in a folder, nothing more.
3 points
Honestly it isn’t a big deal if you just use it on local host. Just make sure cups is sandboxes like it should be. (Systemd)
3 points
Yes, but exactly that was/is the issue of this bug. cups-browsed was attaching itself to every available IP on the system. And cups-browsed can’t only be bind to localhost, it would defeat the whole purpose of that tool. For it to be able to find other printers in the network it needs to be bound to a non-localhost-IP address. So, not much to sandbox
