From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: [9fans] secret stuff
Date: Thu, 13 Jun 2002 15:27:34 +0100 [thread overview]
Message-ID: <e03ac7325f10f6032ed307fc55236565@9fs.org> (raw)
How do I keep the secret key for the tls/ssl certificate safe?
It must be present on the cpu server (or file server) since it needs
to be loaded into factotum some time. I guess it could be done from
a floppy (or similar removeable device) after oboot, and then removed.
However, this prevents unattended reboot. Is making the key owned by
bootes and inaccessible by group and other enough?
next reply other threads:[~2002-06-13 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 14:27 nigel [this message]
2002-06-13 14:42 Russ Cox
2002-06-13 14:47 nigel
2002-06-13 19:41 Richard Miller
2002-06-13 20:56 presotto
2002-06-14 8:02 Richard Miller
2002-06-14 13:26 presotto
2002-06-14 18:52 Richard Miller
2002-06-14 19:07 presotto
2002-06-15 12:49 ` Jim Choate
2002-06-15 15:39 presotto
2002-06-15 16:32 ` Jim Choate
2002-06-15 16:44 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=e03ac7325f10f6032ed307fc55236565@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).