From: Matt Anderson <mra@hp.com>
To: Michael C Thompson <thompsmc@us.ibm.com>
Cc: redhat-lspp@redhat.com, Steve Grubb <sgrubb@redhat.com>,
Linda Knippers <linda.knippers@hp.com>,
Linux Audit <linux-audit@redhat.com>
Subject: Re: Re: cups userspace -- trusted programs?
Date: Mon, 05 Jun 2006 14:10:57 -0400 [thread overview]
Message-ID: <448473B1.5040501@hp.com> (raw)
In-Reply-To: <447F15CC.4070308@us.ibm.com>
Michael C Thompson wrote:
>>> Personally, I think these tools should generate messages since they
>>> are a source for leaking information, and therefore should be
>>> restricted to administrators.
I don't think they should be considered a source for leaking
information. The only thing I see isn't a leak so much as a (extremely
low bandwidth) covert channel of "is the printer enabled or disabled?"
Since the use of these programs is restricted, we're covered under
no-evil-admin.
> Aside from what is *required*, I thought it would be a good thing to log
> the queue/printer enable/disable. However, if cups is logging that, I'm
> not sure it is worth being redundant in our logs.
As long as LogLevel is set to info or higher you'll get a message in
/var/log/cups/error_log like:
[Timestamp] Printer 'foo' stopped by 'root'.
I think I agree with you that its probably not worth being redundant,
but if for someone finds a requirement for this to go to the audit log I
don't see any issues around adding that.
-matt
--
redhat-lspp mailing list
redhat-lspp@redhat.com
https://www.redhat.com/mailman/listinfo/redhat-lspp
next prev parent reply other threads:[~2006-06-05 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 20:06 cups userspace -- trusted programs? Michael C Thompson
2006-05-31 22:54 ` Linda Knippers
2006-06-01 16:29 ` [redhat-lspp] " Michael C Thompson
2006-06-05 18:10 ` Matt Anderson [this message]
2006-06-05 18:25 ` Michael C Thompson
2006-06-05 18:53 ` [redhat-lspp] " Linda Knippers
2006-06-05 19:29 ` Michael C Thompson
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=448473B1.5040501@hp.com \
--to=mra@hp.com \
--cc=linda.knippers@hp.com \
--cc=linux-audit@redhat.com \
--cc=redhat-lspp@redhat.com \
--cc=sgrubb@redhat.com \
--cc=thompsmc@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.