From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] secstore security
Date: Mon, 11 Apr 2005 12:47:07 +0100 [thread overview]
Message-ID: <acbe08de4d055947ee5f5086f9184b94@terzarima.net> (raw)
In-Reply-To: <62c26e89073f7a99463c42198cf6dd62@terzarima.net>
>>of course, since the server just stores files as provided
>>by the client, there is nothing to stop the client making the scheme
>>more elaborate than currently is done for the file `factotum',
and if you're mainly interested in backup, you could (further) encrypt your secstore's files
with a non-trivial key before sending them to 9grid's secstore,
then decrypt them with that key if you ever had to restore them.
of course, in that case using 9grid's secstore on-line directly would require the client
to know to use the extra key.
another variant would be to split the material in some way across
several secstores operated by different people
prev parent reply other threads:[~2005-04-11 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 9:38 Steve Simon
2005-04-11 10:01 ` Devon H. O'Dell
2005-04-11 10:23 ` Charles Forsyth
2005-04-11 11:47 ` Charles Forsyth [this message]
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=acbe08de4d055947ee5f5086f9184b94@terzarima.net \
--to=forsyth@terzarima.net \
--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).