From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Kenshi Muto <kmuto@debian.org>
Cc: 254153@bugs.debian.org, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: Bug#254153: cupsys: SE/Linux required to give user permission to read /var/spool/cups/certs/0
Date: Sat, 3 Jul 2004 08:42:42 +0000 [thread overview]
Message-ID: <20040703084242.GA3099@lkcl.net> (raw)
In-Reply-To: <20040703020944.116BF222FA0@mail.topstudio.co.jp>
On Sat, Jul 03, 2004 at 11:09:43AM +0900, Kenshi Muto wrote:
> Hi,
>
> Sorry for my late response,
>
> At Sun, 13 Jun 2004 10:19:47 +0000,
> Luke Kenneth Casson Leighton wrote:
> > the permissions on SE/Linux are starting from scratch
> > "everything-is-banned".
> >
> > therefore, a quite thorough audit is underway as applications are
> > run and users of Debian / SE/Linux find that they "can't do X".
> >
> > in this instance, "i can't add a printer from KDE's print manager
> > because ordinary users are not given permission to do ANY kind of
> > access to /var/spool/cups."
> >
> > therefore, please could you consider moving the /var/spool/cups/certs
> > to somewhere more appropriate where ordinary can be given read access
> > to it?
>
> Hmm, upstream source uses '/etc/cups/certs', but previous cups
> maintainer changed this by:
> * Moved /etc/cups/certs to /var/spool/cups/certs. Closes: #144887.
>
> I don't know what's best location for this cert file, but how about
> '/var/lib/cups/certs'?
given that cups writes to the certs file every 5 mins, as #144887
says, it's inappropriate for it to be in /etc.
/var/spool/cups is not accessible except by sysadmin.
/var/lib/cups can be created and made user-read-accessible so
that /var/lib/cups/certs can be accessed.
yep, i reckon that's a more appropriate location.
l.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next parent reply other threads:[~2004-07-03 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BkMvA-0004g1-00@newraff.debian.org>
[not found] ` <E1BZS5b-0006MZ-FE@lkcl.net>
[not found] ` <20040703020944.116BF222FA0@mail.topstudio.co.jp>
2004-07-03 8:42 ` Luke Kenneth Casson Leighton [this message]
[not found] ` <handler.254153.D254153.108972409929464.notifdone@bugs.debian.org>
2004-07-13 13:47 ` Bug#254153 acknowledged by developer (Bug#254153: fixed in cupsys 1.1.20final+rc1-1) Luke Kenneth Casson Leighton
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=20040703084242.GA3099@lkcl.net \
--to=lkcl@lkcl.net \
--cc=254153@bugs.debian.org \
--cc=kmuto@debian.org \
--cc=selinux@tycho.nsa.gov \
/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.