9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: [9fans] possible way to have the secstore on the cpu server
Date: Fri, 14 Jun 2002 09:26:01 +0100	[thread overview]
Message-ID: <817ad07b21b28268fd0f8ab9341c6191@9fs.org> (raw)

It seems possible to store the secstore on the cpu server, without the
files being accessible to someone (other than bootes).

The attacker cannot open anything in '#'S as it is owned by bootes.  I
had assumed before that '#'S is generally readable, but it's only
group/user readable.  The service created by kfs is other r/w, so
obviously kfs would be a bad choice.  But, /srv/dos is accessible by
user only, so a small dos filesystem would appear to be unmountable by
anyone other than bootes.

The dossrv would have to be noswap and private, which given the amount
of memory it consumes might be the biggest impediment.

I realise that a separate auth server with no cpu service is
intrinsically more secure, but does the above have any fatal flaws?



             reply	other threads:[~2002-06-14  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14  8:26 nigel [this message]
2002-06-14 16:42 Russ Cox
2002-06-15 14:02 nigel
2002-06-15 15:32 presotto
2002-06-15 15:34 presotto
2002-06-17 10:25 nigel
2002-06-17 11:51 presotto

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=817ad07b21b28268fd0f8ab9341c6191@9fs.org \
    --to=nigel@9fs.org \
    --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).