public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printing
Date: Wed, 14 Jan 2009 08:58:11 +0000	[thread overview]
Message-ID: <200901140858.23992.michaelkintzios@gmail.com> (raw)
In-Reply-To: <496CDF18.2@smash-net.org>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On Tuesday 13 January 2009, Norman Rieß wrote:
> Peter Humphrey schrieb:

> >> package.use
> >> net-print/cups jpeg nls pam png ppds ssl tiff X
> >
> > So you do have ldap specified. I'll try recompiling cups with ldap and
> > see what that does. Thanks.
>
> Yes, but i do not use ldap in my network.

Peter, ldap is only required if you are authenticating clients on your LAN/WAN 
using an ldap server.  If you had hundreds of clients and a need to manage 
frequently changing client membership and passwds, then ldap would be 
desirable to manage them effectively.

In your case you just need to control access to your cups server by means of 
the allow/deny wrappers in /etc/cups/conf.d for machines in your LAN and let 
them through the iptables on the server machine.

Increasing the verbosity of the access and error cups logs will show you what 
you need to (re)configure.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-14 18:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 15:39 [gentoo-user] Network printing Peter Humphrey
2009-01-06 17:04 ` Mark Knecht
2009-01-07 12:08   ` Peter Humphrey
2009-01-07 14:20     ` BRM
2009-01-10 12:15       ` Peter Humphrey
2009-01-10 12:56         ` Norman Rieß
2009-01-12 10:44           ` Peter Humphrey
2009-01-12 11:24             ` Norman Rieß
2009-01-12 20:12               ` Norman Rieß
2009-01-13 10:38                 ` Peter Humphrey
2009-01-13 14:19                   ` Norman Rieß
2009-01-13 17:46                     ` Peter Humphrey
2009-01-13 18:36                       ` Norman Rieß
2009-01-14  8:58                         ` Mick [this message]
2009-01-15 10:39                           ` Peter Humphrey
2009-01-15 14:50                             ` Mick
2009-01-12 14:25             ` BRM
2009-01-13 10:42               ` Peter Humphrey
2009-01-07 15:03     ` Mark Knecht
2009-01-06 18:44 ` BRM
2009-01-19 16:08 ` [gentoo-user] Network printing -- Solved Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2008-12-22 11:25 [gentoo-user] Network printing Peter Humphrey
2008-12-22 18:00 ` BRM
2008-12-23 11:53   ` Peter Humphrey
2008-12-24  0:03     ` Mick
2008-12-24  9:25       ` Peter Humphrey
2008-12-24 10:45         ` Mick
2008-12-24 11:45           ` Peter Humphrey
2008-12-24 19:31             ` Mark Knecht
2008-12-28 12:47               ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200901140858.23992.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox