All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: Re: New Apache policy
Date: Tue, 29 Oct 2002 18:45:39 +0100	[thread overview]
Message-ID: <20021029184539.A16049@lemuria.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0210291146020.29605-100000@raven>; from sds@tislabs.com on Tue, Oct 29, 2002 at 12:09:30PM -0500

On Tue, Oct 29, 2002 at 12:09:30PM -0500, Stephen Smalley wrote:
> > The main reason for giving the client tools a domain was to unify
> > server and client access, i.e. set up the repository so that it can
> > only be accessed by the proper tools. As with CVS, tampering directly
> > with the repository will corrupt it.
> 
> It would offer some limited integrity protection in terms of ensuring that
> the transactions on the repository are well-formed (i.e. only permitting
> transactions implemented via svn, svnlock, or svnadmin commands).  But it

Correct. It protects from mistakes, not malicious intent.

I still see the value in it, especially given that Subversion is still
in development - who knows what kinds of access controls and other fine
print the team might still add? Running in its own domain, the policy
is ready for whatever they come up with.

Also, I may think about restricting _local_ access for these tools,
because they are connecting outwards to potentially hacked and/or
malicious servers.


> > Also, this leaves the option of restricting access to the repository by
> > restricting access to the tools by using either unix or SELinux
> > permissions.
> 
> With a client program domain, this would take the form of only specifying
> svn_domain() for certain user domains as opposed to all of them.  Without
> a client program domain, it would simply consist of only allowing certain
> user domains to directly access the repository type.

You're right, it doesn't make much of a difference.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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.

  reply	other threads:[~2002-10-29 17:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 14:06 New Apache policy Tom
2002-10-24 14:43 ` Russell Coker
2002-10-24 15:15   ` Tom
2002-10-25 14:42   ` Tom
2002-10-29 16:03     ` Stephen Smalley
2002-10-29 16:36       ` Tom
2002-10-29 17:09         ` Stephen Smalley
2002-10-29 17:45           ` Tom [this message]
2002-10-29 18:37             ` Russell Coker
2002-10-29 18:50               ` Tom

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=20021029184539.A16049@lemuria.org \
    --to=tom@lemuria.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.