Ron Stodden wrote:
>
> Till Kamppeter wrote:
>
> > I didn't need to change any "host" files. Which "host" files did you
> > modify and how. What happened when you didn't do it. Which versions of
> > the packages are you using (update from the Cooker and try again
> > perhaps). Which security level are you using.
>
> /etc/hosts.lpd must contain a list of clients permitted to use this
> local printer. Without this set up you cannot remote print. The
> installer makes no attempt to set this up, or even to create the
> file. (Smack!).
>
> I suspect the above may apply to lpd remote printing only. How does
> CUPS manage remote client authentication? Surely there is an
> equivalent file, which can only be set up manually, since only the
> system administrator knows who is permitted access to each remote
> printer?
>
Se the file /etc/cups/cupsd.conf or better start "kupsdconf" as root and
look especially into the security section. There you can restrict the
access permission to the whole server, the server administration, all
printers, all classes, or every individual printer or class to the
desired machines, or exclude machines from being allowed. For user
restrictions you can create a group and make all permitted users member
of it then give a group permission to the printer with "kupsdconf".
Password protection based on the Unix accounts of the users (or on a
special user account on the server) is possible by "basic
authentication" password protection by special CUPS accounts with
"digested authentification". "Basic authentication" as root of the
server is default for the server administration.
Till
