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: Thu, 30 Oct 2003 22:19:27 +0100 [thread overview]
Message-ID: <20031030221926.E27196@lemuria.org> (raw)
In-Reply-To: <200310310610.14859.russell@coker.com.au>; from russell@coker.com.au on Fri, Oct 31, 2003 at 06:10:14AM +1100
On Fri, Oct 31, 2003 at 06:10:14AM +1100, Russell Coker wrote:
> I would like some feedback on how people feel about having files/dirs under a
> user's home directory that they can't unlink or rename.
Trojan protection comes to mind immediately. Any files that are
automatically executed or such like, which contains .bashrc and its
bretheren, but also .forward and others.
It might be good to not have these modifyable from the standard user_r,
but only from a special different role to guarantee that mistake or
malicious code can not mess them up.
Other than that, we should definitely provide the infrastructure. On
many systems, the admin might want to force some settings or start
scripts.
--
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.
next prev parent reply other threads:[~2003-10-30 21:26 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 [this message]
2003-10-30 23:47 ` Brian May
2003-10-31 8:46 ` Tom
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=20031030221926.E27196@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.