9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] log oversight
Date: Mon, 16 Mar 2009 00:23:59 -0400	[thread overview]
Message-ID: <20090316042359.GI22497@masters6.cs.jhu.edu> (raw)
In-Reply-To: <4D743982-1C38-4BBC-B77E-DCBB5791361A@corpus-callosum.com>

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

On Sun, Mar 15, 2009 at 08:49:50PM -0500, Jeff Sickel wrote:
> I've just built out a new Plan 9 cpu/auth server and noticed that others 
> are able to write to the logs.  Is this intentional or just an  
> oversight?

It is intentional, AFAIK.

An alternative for the paranoid perhaps would be to make an additional fs
(in fossil) containing the log files.  This fs could be set to accept only
the hostowner's credentials for attach requests.  The hostowner, meanwhile,
when constructing namespaces, could bind the right file(s) into the log
directory.  I haven't thought it through in more detail than that, but if I
were to engineer a replacement, that's how I'd start.  HTH.

--nwf;

[-- Attachment #2: Type: application/pgp-signature, Size: 204 bytes --]

  parent reply	other threads:[~2009-03-16  4:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16  1:49 Jeff Sickel
2009-03-16  2:35 ` balaji
2009-03-16  3:04   ` erik quanstrom
2009-03-16  3:18     ` ron minnich
2009-03-16  3:55       ` J.R. Mauro
2009-03-16  4:31         ` Alex Efros
2009-03-16  6:30         ` ron minnich
2009-03-16 15:06           ` J.R. Mauro
2009-03-16  4:23 ` Nathaniel W Filardo [this message]
2009-03-16  4:36   ` Jeff Sickel
2009-03-16 13:37   ` erik quanstrom

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=20090316042359.GI22497@masters6.cs.jhu.edu \
    --to=nwf@cs.jhu.edu \
    --cc=9fans@9fans.net \
    /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).