From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] pptp_t vs pppd_t
Date: Tue, 03 Jul 2012 07:18:06 -0400 [thread overview]
Message-ID: <4FF2D4EE.6050805@redhat.com> (raw)
In-Reply-To: <201207031543.56296.russell@coker.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/03/2012 01:43 AM, Russell Coker wrote:
> Is there a real benefit in having separate domains for pptp and pppd?
>
> The access that they have is very similar and the differences are things
> that aren't so significant (EG pptp_t denied access to
> pppd_devpts_t:chr_file).
>
> Also both the programs can run each other (the policy allows pppd to run
> pptpd and in my test network pptpd needs to run pppd) which limits the
> ability to create a useful separation.
>
> I think it would be best if we merged the two domains.
>
I am always for merging domains together. I think we have far too many
domains that basically have the security domain and just add complexity.
Fedora consolidated all of the "spam" domains also.
I really believe we should consolidate the mail domains. mail_t instead of
sendmail_t, postfix_t, qmail_t, dovecot_t, courier_t ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/y1O4ACgkQrlYvE4MpobPtpgCgpl0i5SgNbakzYEOO8V0tDvAN
lTYAoNVw17S4dCdmCdbfqFD1zUjEfPo9
=qWw4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-07-03 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 5:43 [refpolicy] pptp_t vs pppd_t Russell Coker
2012-07-03 11:18 ` Daniel J Walsh [this message]
2012-07-03 11:47 ` Miroslav Grepl
2012-07-03 11:55 ` Russell Coker
2012-07-03 13:44 ` Christopher J. PeBenito
2012-07-03 11:53 ` Russell Coker
2012-07-03 15:20 ` Sven Vermeulen
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=4FF2D4EE.6050805@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.