All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: user's access to files in their own home directory
Date: Fri, 31 Oct 2003 09:46:35 +0100	[thread overview]
Message-ID: <20031031094635.F1540@lemuria.org> (raw)
In-Reply-To: <20031030234711.GA31194@snoopy.apana.org.au>; from bam@snoopy.apana.org.au on Fri, Oct 31, 2003 at 10:47:12AM +1100

On Fri, Oct 31, 2003 at 10:47:12AM +1100, Brian May wrote:
> This would seem to imply a useability/security tradeoff that is
> dependant on the security requirements of the computer.
> 
> However, what files/dirs are you thinking of?

Anyone remember my "quarantine download dir" proposal from earlier this
year?

The basic idea:

~/Downloads/		system_u:object_r:untrusted_dir_t
file_type_auto_trans(.*, untrusted_dir_t, untrusted_file_t)
domain_auto_trans(.*, untrusted_file_t, untrusted_t)

And untrusted_t has a very restricted set of permissions. Especially it
can write nowhere except in untrusted_dir_t and /tmp. That way I can
"try out" stuff I found on the net.


-- 
PGP/GPG key: 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:[~2003-10-31  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 19:10 user's access to files in their own home directory Russell Coker
2003-10-30 21:19 ` Tom
2003-10-30 23:47 ` Brian May
2003-10-31  8:46   ` Tom [this message]
2003-10-31 19:17   ` Russell Coker

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=20031031094635.F1540@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.