From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: Re: revising the su decision]
Date: Sat, 13 Jul 2002 09:29:53 +0200 [thread overview]
Message-ID: <20020713092953.L26382@lemuria.org> (raw)
On Sat, Jul 13, 2002 at 06:04:56AM +0200, Russell Coker wrote:
> > c) give your remote/install user write priviledges for /var/install
>
> If someone can write to /var/install in that case, then why not just allow
> them to login directly with full admin privs?
>
> Writing a RPM or DEB package to take over or destroy a system is easy
> enough...
the point is that if you want to, you can do sanity checks before
installing the packages.
automated remote software updates are always essentially equal to
putting the root password into /etc/motd - but if the priviledged part
runs on the local machine, you at least do have a chance.
--
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
--
You have received this message because you are subscribed to the selinux 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-07-13 7:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020713092953.L26382@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.