Re: cups, problem mit require group
Hartmut schrieb:
> Hallo,
>
> ich habe folgendes Problem mit cups:
> Mein Benutzer befindet sich in der Gruppe printers. Wenn ich nun in der
> Config die Zeile "Require group printers"
> <Location />
> # Require group printers
> Order allow,deny
> Allow localhost
> Allow 172.16.0.0/24
> </Location>
> auskommentiere funktioniert alles, wenn ich sie mit rein nehme bekomme
> ich beim Client die Fehlermeldung "Keine Zugriffsrechte".
>
> Hat jemand eine Idee woran das liegen könnte? Anbei meine cupsd.conf
>
> Gruß und Danke
> Hartmut
>
>
>
> --/etc/cups/cupsd.conf----------------------------------------------------
> #
> #
> # Sample configuration file for the Common UNIX Printing System (CUPS)
> # scheduler. See "man cupsd.conf" for a complete description of this
> # file.
> #
>
> # Log general information in error_log - change "info" to "debug" for
> # troubleshooting...
> LogLevel warning
> #LogLevel debug
>
> # Administrator user group...
> SystemGroup lpadmin
>
> # Only listen for connections from the local machine.
> Listen localhost:631
> Listen 172.16.0.104:631
> Listen /var/run/cups/cups.sock
>
> # Show shared printers on the local network.
> Browsing On
> BrowseOrder allow,deny
> BrowseAllow @LOCAL
>
> # Default authentication type, when authentication is required...
> DefaultAuthType Basic
> DefaultEncryption Required
>
> # Restrict access to the server...
> <Location />
> # Require group printers
> Order allow,deny
> Allow localhost
> Allow 172.16.0.0/24
> </Location>
>
> # Restrict access to the admin pages...
> <Location /admin>
> Encryption Required
> Order allow,deny
> Allow localhost
> Allow 172.16.0.0/24
> </Location>
>
> # Restrict access to configuration files...
> <Location /admin/conf>
> AuthType Basic
> # Require user @SYSTEM
> Order allow,deny
> Allow localhost
> Allow 172.16.0.0/24
> </Location>
>
> # Set the default printer/job policies...
> <Policy default>
> # Job-related operations must be done by the owner or an adminstrator...
> <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job
> Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription
> Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
> Suspend-Current-Job Resume-Job CUPS-Move-Job>
> # Require user @OWNER @SYSTEM
> # Require group printers
> Order deny,allow
> Allow 172.16.0.0/24
> </Limit>
>
> # All administration operations require an adminstrator to authenticate...
> <Limit Pause-Printer Resume-Printer Set-Printer-Attributes
> Enable-Printer Disable-Printer Pause-Printer-After-Current-Job
> Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer
> Restart-Printer Shutdown-Printer Startup-Printer Promote-Job
> Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class
> CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default>
> AuthType Basic
> # Require user @SYSTEM
> # Require group printers
> Order deny,allow
> Allow 172.16.0.0/24
> </Limit>
>
> # Only the owner or an administrator can cancel or authenticate a job...
> <Limit Cancel-Job CUPS-Authenticate-Job>
> # Require user @OWNER @SYSTEM
> # Require group printers
> Order deny,allow
> Allow 172.16.0.0/24
> </Limit>
>
> <Limit All>
> Order deny,allow
> Allow 172.16.0.0/24
> </Limit>
> </Policy>
>
> #
> #
>
> #
> # Printcap: the name of the printcap file. Default is /etc/printcap.
> # Leave blank to disable printcap file generation.
> #
>
> Printcap /var/run/cups/printcap
>
> #
> # PrintcapFormat: the format of the printcap file, currently either
> # BSD or Solaris. The default is "BSD".
> #
>
> #PrintcapFormat BSD
> #PrintcapFormat Solaris
>
> #
> # PrintcapGUI: the name of the GUI options panel program to associate
> # with print queues under IRIX. The default is "/usr/bin/glpoptions"
> # from ESP Print Pro.
> #
> # This option is only used under IRIX; the options panel program
> # must accept the "-d printer" and "-o options" options and write
> # the selected printer options back to stdout on completion.
> #
>
> #PrintcapGUI /usr/bin/glpoptions
> ------------------------------------------------------------------------------
inzwischen habe ich folgendes heraus gefunden. Wenn ich
__DefaultEncryption Required__ durch __DefaultEncryption Never__
ersetze, scheint es problemlos zu gehen. Könnte es sein, dass die
Clients (Windows XP Prof.) ein Problem mit der Verschlüsselung haben?
Gruß
Hartmut
Reply to: