On 10/30/2014 08:29 AM, Didier 'OdyX' Raboud wrote: > Hi Michal, and thanks for your bugreport, > > I think I understand the problem you're having, let's see. > > Le mercredi, 22 octobre 2014, 13.12:51 Michal Hocko a écrit : >> (..) >> Of course I had >> BrowseAllow all >> >> present and that caused all remote printers being disallowed by >> default. > > Are you saying that all "BrowseAllow" stanzas _but_ "BrowseAllow all" > should have been taken over by cups-browsed? > >> Maybe postinstall script can ask whether such an option should be >> added if those options cannot be ignored by default. > > We try to avoid doing explicit prompts unless really _really_ important, > we're not in such a case here… > > Till: What would you think of the above proposal? It kinda-makes sense > for me: in CUPS < 1.5 meaning, "BrowseAllow all" meant "accept packets > from anywhere", but in cups-browsed meaning, this is completely > discarded, and the same meaning is achieved without any 'BrowseAllow' > stanza. I'd welcome your input there. >
The "Browse..." directive implementation was done by Tim Waugh as part of the legacy CUPS broadcasting/browsing support. I do not know the exact details, especially not of combinations of various lines. I only know that all clients are allowed if no line is given. Tim, can you help here? Thanks, Till P. S.: Tim, please use "Reply all" so that your answer gets tracked with the Debian bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
