From: "Russ Cox" <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Venti and the hash / public key in plan9
Date: Mon, 6 Feb 2006 11:58:49 -0500 [thread overview]
Message-ID: <E1F69hR-0003Y6-43@x40.swtch.com> (raw)
In-Reply-To: <45219fb00602060836q7aa16bf7q@mail.gmail.com>
> Hi... I've been reading the papers about Venti. There is an
> explanation about the low probability of the repetition of a hash
> string in a normal-sized nowadays hard disk. Anyway I've don't
> understood what does Venti do when a hash is found in the stored
> blocks, and the contents of the blocks are different (the
> low-probability case). I imagine there is some code which does not
> give a data-loss... Can someone give a small explanation about that?
It responds to the write RPC with an error.
> And also about public key management in plan9 for (at least) 9p
> connections. I've seen in the paper regarding Security that there's
> used only Shared-key authentication (p9sk1). Maybe there's something
> new in the actual distribution of plan9.
p9sk1 is only an authentication protocol.
Some 9P sessions are encrypted using TLS/SSL.
We just match the SHA1 hash of the remote public key against
a local list of okayed hashes. There is no attempt to
delve into the whole key hierarchy. This is discussed
in the Security paper.
Russ
next prev parent reply other threads:[~2006-02-06 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 16:36 Lluís Batlle
2006-02-06 16:58 ` Russ Cox [this message]
2006-02-06 17:16 ` Lluís Batlle
2006-02-06 17:21 ` "Nils O. Selåsdal"
2006-02-06 17:33 ` uriel
2006-02-06 17:37 ` Ronald G Minnich
2006-02-06 17:55 ` Lluís Batlle
2006-02-06 19:45 ` Russ Cox
2006-02-06 17:51 ` andrey mirtchovski
2006-02-06 19:49 ` Joel Salomon
2006-02-06 17:25 ` Ronald G Minnich
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=E1F69hR-0003Y6-43@x40.swtch.com \
--to=rsc@swtch.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).