Lee wrote: > uh oh .. > "It would be as well to check whether any functioning print queues > have been automatically installed by cups-browsed prior to a manual > setup. This can be done with > lpstat -a" > > $ lpstat -a > Canon_MG3600_series accepting requests since Sat Aug 3 00:00:28 2024 > HP_ENVY_5540_series_20A070_ accepting requests since Sat Aug 3 00:00:28 2024
Not terrible. The only conflict with multiple definitions of the same printer is when multiple people try to use them simultaneously. > I'd have to go back to an /etc/nsswitch.conf with > hosts: files dns > and then manually configure the print queues. Correct? Or re-trigger automatic configs, yes. > > and use either > > the web interface on port 631 or system-config-printer in a GUI > > to set up your printer. If it's recent, it can probably use the > > ipp driver; if it is middle-aged, it can probably be used via > > the port 9100 lp system. > > Thanks for the info. I'm not sure that manual configuration is all > that much better than the automatic stuff tho.. it seems like if > someone can get on my network and respond to mDNS queries I've got > worse problems than them impersonating a printer. Let's say that the problems start with impersonating a printer and get more severe from there. > Am I missing something or does manually configuring printer queues > just remove my print queue dependency on avahi / mDNS? > I can see not wanting mDNS in a work environment, but at home?? I > don't see how it improves my security all that much. It does not particularly affect security in this scenario, no. I was offering answers to your questions rather than polict recommendations. -dsr-
