From: Michael C Thompson <thompsmc@us.ibm.com>
To: Linux Audit <linux-audit@redhat.com>,
Linda Knippers <linda.knippers@hp.com>,
Steve Grubb <sgrubb@redhat.com>,
mra@hp.com, redhat-lspp@redhat.com
Subject: cups userspace -- trusted programs?
Date: Wed, 31 May 2006 15:06:13 -0500 [thread overview]
Message-ID: <447DF735.9090706@us.ibm.com> (raw)
Hey all,
I'm wondering if the intent of the cups userspace tools are to be
trusted programs? Specifically I'm curious about cupsaccept, cupsreject,
cupsenable and cupsdisable. The reason I ask is because if they are
supposed to be trusted programs, they don't generate unique audit
messages like other programs.
Personally, I think these tools should generate messages since they are
a source for leaking information, and therefore should be restricted to
administrators.
Thanks,
Mike
--
redhat-lspp mailing list
redhat-lspp@redhat.com
https://www.redhat.com/mailman/listinfo/redhat-lspp
next reply other threads:[~2006-05-31 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 20:06 Michael C Thompson [this message]
2006-05-31 22:54 ` cups userspace -- trusted programs? Linda Knippers
2006-06-01 16:29 ` [redhat-lspp] " Michael C Thompson
2006-06-05 18:10 ` Matt Anderson
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=447DF735.9090706@us.ibm.com \
--to=thompsmc@us.ibm.com \
--cc=linda.knippers@hp.com \
--cc=linux-audit@redhat.com \
--cc=mra@hp.com \
--cc=redhat-lspp@redhat.com \
--cc=sgrubb@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox