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: Re: [9fans] secstore
Date: Wed, 15 May 2002 13:26:52 +0100	[thread overview]
Message-ID: <34cf4c7e79306f17b5d765989db20dba@9fs.org> (raw)

In the light on Lucio's comment, if I was paranoid, I would need to prevent
the casual user from binding '#'S, or rather, opening /dev/sdC0/fs, since
they could root around in there, rather than use /srv/kfs.

So, for the paranoid, a separate auth server is more sensible. At least,
those paranoid about security. Those of us more paranoid about heat, noise,
and the electricty bill will probably choose a bit of hacking of pccpu.

Assuming the kfs on the cpu server is not protected, the presumably,
keeping secstore on the fileserver is no more insecure?

I'm really only interested in the convenience of having to give a single
password all day.


             reply	other threads:[~2002-05-15 12:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 12:26 nigel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-15 18:22 rsc
2002-05-15 16:31 presotto
2002-05-15 16:30 jmk
2002-05-15 16:23 presotto
2002-05-15 15:36 anothy
2002-05-15 15:02 presotto
2002-05-15 14:15 rob pike, esq.
2002-05-15 14:43 ` Lucio De Re
2002-05-15 14:14 presotto
2002-05-15 14:37 ` Lucio De Re
2002-05-15 13:33 presotto
2002-05-15 13:59 ` Lucio De Re
2002-05-15 12:33 presotto
2002-05-15 13:09 ` Lucio De Re
2002-05-15 12:17 presotto
2002-05-15 11:58 nigel
2002-05-15 12:16 ` Lucio De Re
2002-05-15 11:55 presotto
2002-05-15 11:45 forsyth
2002-05-15 11:19 nigel

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=34cf4c7e79306f17b5d765989db20dba@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).