From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] who can write venti archives?
Date: Thu, 11 Dec 2003 13:23:38 +0000 [thread overview]
Message-ID: <323520958f5dc4952a92683a3a2c47bd@caldo.demon.co.uk> (raw)
In-Reply-To: <1cd1004491626fa5f20920bdf2d36d40@granite.cias.osakafu-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
the user running fossil needs permssion to read and write
the fossil disk partition, and do whatever is required
(typically connect over the network) to venti, if that's being used.
fossil then imposes access restrictions on its
clients when they access files through 9P connections,
including connections by the user running fossil (who has
no extra permissions when accessing that file system structure)
venti currently imposes few restrictions, except that
clients need to know the protocol and some scores (to read).
to secure the fossil+venti combination to a level
similar to the old file server you'd probably want
to prohibit all but fossil and authsrv-related connections
to the file serving machine; in particular venti wouldn't
appear directly on the network.
[-- Attachment #2: Type: message/rfc822, Size: 2413 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] who can write venti archives?
Date: Thu, 11 Dec 2003 19:44:59 +0900
Message-ID: <1cd1004491626fa5f20920bdf2d36d40@granite.cias.osakafu-u.ac.jp>
Today, I found I'm not clear who writes archive files
to venti.
In the Ken's file server, we have a different kernal for file
server, and I didn't bother with this question. It may also
be fault either, I don't know.
In the fossil+venti case, venti and fossil processes are running
as a user process, which means there is a real person who
has limited previlege of course, and then, s/he has no permission
to some files or directories. How s/he can makes store those
files/directories to venti archives?
Kenji
next prev parent reply other threads:[~2003-12-11 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 10:44 okamoto
2003-12-11 13:23 ` Charles Forsyth [this message]
2003-12-11 14:20 ` Fco.J.Ballesteros
2003-12-12 2:03 ` okamoto
2003-12-12 3:19 ` Russ Cox
2003-12-12 4:03 ` okamoto
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=323520958f5dc4952a92683a3a2c47bd@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).