From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <323520958f5dc4952a92683a3a2c47bd@caldo.demon.co.uk> To: 9fans@cse.psu.edu Subject: Re: [9fans] who can write venti archives? From: Charles Forsyth In-Reply-To: <1cd1004491626fa5f20920bdf2d36d40@granite.cias.osakafu-u.ac.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-zeadtisasmqjicxijoyhrzjasy" Date: Thu, 11 Dec 2003 13:23:38 +0000 Topicbox-Message-UUID: 9f60a602-eacc-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-zeadtisasmqjicxijoyhrzjasy Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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. --upas-zeadtisasmqjicxijoyhrzjasy Content-Type: message/rfc822 Content-Disposition: inline Return-path: <9fans-admin@cse.psu.edu> Received: from punt-3.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk id 1AUOK5-0000fU-63; Thu, 11 Dec 2003 10:46:38 +0000 Received: from [130.203.4.6] (helo=mail.cse.psu.edu) by punt-3.mail.demon.net with esmtp id 1AUOK5-0000fU-63 for forsyth@caldo.demon.co.uk; Thu, 11 Dec 2003 10:45:33 +0000 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id 7C61F19B44; Thu, 11 Dec 2003 05:45:26 -0500 (EST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 60CE919D9F; Thu, 11 Dec 2003 05:45:11 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id A7CCB19D70; Thu, 11 Dec 2003 05:44:51 -0500 (EST) Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.101.69]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 6A464199DB for <9fans@cse.psu.edu>; Thu, 11 Dec 2003 05:44:39 -0500 (EST) Message-ID: <1cd1004491626fa5f20920bdf2d36d40@granite.cias.osakafu-u.ac.jp> To: 9fans@cse.psu.edu From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: [9fans] who can write venti archives? Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 11 Dec 2003 19:44:59 +0900 X-Spam-Status: No, hits=0.8 required=5.0 tests=NO_REAL_NAME version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) 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 --upas-zeadtisasmqjicxijoyhrzjasy--