From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] secstore
Date: Wed, 15 May 2002 08:17:40 -0400 [thread overview]
Message-ID: <2e0ad0b6969180f7dcdbd609aa3f5bbf@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
I'ld do the same thing for keyfs also, i.e., put /adm/keys and /adm/secsore
on the kfs and not make them visible to most processes. You'll have
to protect /srv/kfs and /srv/kfs.cmd also so that only the hostowner
can open them.
[-- Attachment #2: Type: message/rfc822, Size: 1428 bytes --]
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] secstore
Date: Wed, 15 May 2002 12:58:16 +0100
Message-ID: <80dc9d46780953d37104e05c11fbed0f@9fs.org>
So a suitable solution for a combined cpu/auth server would be to use
kfs and bind it over /adm/secstore for the secstored process only?
I note that my cpu sever has a 15Gb disk which is only used for swap
at the moment so I suppose I ought to make better use of it.
next reply other threads:[~2002-05-15 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 12:17 presotto [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:26 nigel
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=2e0ad0b6969180f7dcdbd609aa3f5bbf@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--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).