9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: johnny@sorosj.hd.free.fr
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/sources/contrib/
Date: Sun, 18 Nov 2007 22:23:15 +0100	[thread overview]
Message-ID: <be7f4b5d38eea975d35cf597113dd685@sorosj.hd.free.fr> (raw)
In-Reply-To: <df49a7370711180333i109670a9k4ce5c0ce557114a1@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 439 bytes --]

I might be missing something again, but if someone set's a 600 permission, doen't that mean only the user himself can see the file? I don't understand why this is relevant, as if that's the case, noone else can see the file. The only issue is if the user who does the vac backup backs up his own contrib directory logged in as himself.
As for backing up stand alone directories and files, doesn't vac do that just fine?
Cheers!
Johnny

[-- Attachment #2: Type: message/rfc822, Size: 4201 bytes --]

From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] /n/sources/contrib/
Date: Sun, 18 Nov 2007 11:33:40 +0000
Message-ID: <df49a7370711180333i109670a9k4ce5c0ce557114a1@mail.gmail.com>

On Nov 17, 2007 10:00 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> after a fossil dump, the skinny on the arena offsets and the score
> of the superblock (or whatever fossil calls it) could be relayed
> to the mirror site [...]

you'd have to make sure if you did that that people putting stuff in
contrib were aware
that setting a file's permissions to 600 would have no effect on anyone's
ability to read it. i realise that it is called "contrib" but it does *look*
as if file permissions should work.

i've always wondered if there might be some way of changing venti
to make it more secure for multi-user access, so accidentally sharing
a root score
isn't quite such a terrible thing.

  parent reply	other threads:[~2007-11-18 21:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-17  5:35 lucio
2007-11-17 18:05 ` andrey mirtchovski
2007-11-17 18:55   ` lucio
2007-11-17 18:56   ` lucio
2007-11-17 22:00   ` erik quanstrom
2007-11-18  4:39     ` lucio
2007-11-18  5:08       ` erik quanstrom
2007-11-18  5:30         ` lucio
2007-11-18 10:25           ` johnny
2007-11-18 11:04             ` lucio
2007-11-18 11:33     ` roger peppe
2007-11-18 13:24       ` lucio
2007-11-18 14:18       ` erik quanstrom
2007-11-18 18:17       ` johnny
2007-11-19 16:29         ` roger peppe
2007-11-18 21:23       ` johnny [this message]
2007-11-17 18:13 ` Uriel
2007-11-17 18:58   ` lucio
2007-11-18 15:17 ` Russ Cox
2007-11-18 15:29   ` erik quanstrom
2007-11-18 18:26     ` Francisco J Ballesteros
2007-11-19  2:15     ` Russ Cox
2007-11-19 17:38       ` erik quanstrom
2007-11-19 17:53         ` Russ Cox
2014-05-23  7:20 David Hoskin

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=be7f4b5d38eea975d35cf597113dd685@sorosj.hd.free.fr \
    --to=johnny@sorosj.hd.free.fr \
    --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).