From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] capability-based design (Re: permissions idea)
Date: Thu, 4 Oct 2001 20:28:24 +0100 [thread overview]
Message-ID: <20011004191609.B7DB9199B5@mail.cse.psu.edu> (raw)
> the app must asks permission (from the OS, which
> then might ask the user) before doing anything significant to the user's
> software environment.
surely that assumes that the user wouldn't just automatically accept
any reasonable-sounding request to open a file (i know i would,
especially if i had several hundred per day).
might it not be better just to use filterfs to make sure that an
application can't see the files i want to hide from it? you could
even add an interface so that an application could request that a
certain file/filetree be made visible; that could even trigger a
request to the user if required.
capabilities (and ACLs) seem to me like they'd be a maintenance
nightmare. i can barely remember to chmod my personal files 600...
rog.
next reply other threads:[~2001-10-04 19:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 19:28 rog [this message]
2001-10-04 20:27 ` Richard
2001-10-04 20:33 ` Richard
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 2:06 okamoto
2001-10-08 18:16 Sape Mullender
2001-10-08 18:18 ` Lucio De Re
2001-10-05 17:12 Russ Cox
2001-10-05 8:13 nigel
2001-10-05 16:44 ` Richard
2001-10-05 5:31 nigel
2001-10-05 7:40 ` Richard
2001-10-08 9:36 ` Thomas Bushnell, BSG
2001-10-05 4:00 okamoto
2001-10-08 16:53 ` Maarit Maliniemi
2001-10-04 23:57 Richard
2001-10-04 21:59 forsyth
2001-10-04 23:29 ` Richard
2001-09-28 1:06 [9fans] on the topic of viruses dmr
2001-10-01 16:13 ` permissions idea (Re: [9fans] on the topic of viruses) Matthew Hannigan
2001-10-02 8:34 ` Douglas A. Gwyn
2001-10-04 18:36 ` [9fans] capability-based design (Re: permissions idea) Richard
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=20011004191609.B7DB9199B5@mail.cse.psu.edu \
--to=rog@vitanuova.com \
--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).