From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] unconfined_cronjob_t et al
Date: Fri, 19 Aug 2011 06:29:45 -0400 [thread overview]
Message-ID: <4E4E3B19.7080302@redhat.com> (raw)
In-Reply-To: <201108181731.39986.russell@coker.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/18/2011 03:31 AM, Russell Coker wrote:
> Is anyone actually making use of domains such as
> unconfined_cronjob_t?
>
> Is there any reason why I shouldn't just unilaterally remove them
> from the Debian policy for Squeeze regardless of what Red Hat and
> upstream are doing?
>
> It seems to me that using a different domain for cron jobs causes
> pain with no gain.
>
I don't think so. I believe cronjobs in Red Hat os's are running
cronjobs as the usertype. I would say this should just be removed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5OOxkACgkQrlYvE4MpobMmlACcCDzLvpMW7LQ+BQPcxQtMrgYR
hsUAoNehIAV+dNUWPtI0tAEAyHrfk2bn
=xqvS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-19 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 7:31 [refpolicy] unconfined_cronjob_t et al Russell Coker
2011-08-18 7:35 ` Russell Coker
2011-08-19 10:29 ` Daniel J Walsh [this message]
2011-08-23 14:05 ` Christopher J. PeBenito
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=4E4E3B19.7080302@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.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.