From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: permissions idea (Re: [9fans] on the topic of viruses)
Date: Tue, 2 Oct 2001 08:34:41 +0000 [thread overview]
Message-ID: <3BB8BCC0.CC5C9FC2@null.net> (raw)
In-Reply-To: <3BB89647.BD039EE5@zip.com.au>
Matthew Hannigan wrote:
> ... perhaps we could have ...
I don't think any scheme with fixed categories of trust
can suffice for heavy-duty security. Even the military
(fixed) "levels" are augmented by orthogonal (freely
created) "compartments" to attain betten control over
access. The big problem in automating a security
policy is in stopping people or programs from taking it
upon themselves to circumvent the policy. The only
viable solution I know of is for *every* mode of access
to *every* object to require the accessor to possess an
appropriate "capability". Capability-based security is
an old idea, but there have some recent developments
that may make it more practical.
next prev parent reply other threads:[~2001-10-02 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 1:06 [9fans] on the topic of viruses dmr
2001-09-28 9:58 ` Boyd Roberts
2001-10-01 16:13 ` permissions idea (Re: [9fans] on the topic of viruses) Matthew Hannigan
2001-10-01 16:18 ` Matthew Hannigan
2001-10-02 8:34 ` Douglas A. Gwyn [this message]
2001-10-02 15:11 ` Matthew Hannigan
2001-10-04 18:36 ` [9fans] capability-based design (Re: permissions idea) Richard
2001-09-28 14:23 ` [9fans] on the topic of viruses Bobby Dimmette
2001-09-28 18:44 ` Boyd Roberts
2001-09-28 20:35 ` Bobby Dimmette
2001-10-01 9:55 ` Douglas A. Gwyn
2001-10-01 10:40 ` Boyd Roberts
2001-10-01 9:55 ` Douglas A. Gwyn
2001-10-02 15:37 permissions idea (Re: [9fans] on the topic of viruses) presotto
2001-10-03 1:14 okamoto
2001-10-04 9:11 ` Douglas A. Gwyn
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=3BB8BCC0.CC5C9FC2@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).