[e-cvs] cvs commit: e/doc/elib/distrib/captp unibus.html
markm@eros.cs.jhu.edu
markm@eros.cs.jhu.edu
Mon, 20 Aug 2001 19:53:41 -0400
markm 01/08/20 19:53:41
Modified: doc/elib/distrib/captp unibus.html
Log:
typo. Thanks Norm.
Revision Changes Path
1.8 +7 -7 e/doc/elib/distrib/captp/unibus.html
Index: unibus.html
===================================================================
RCS file: /cvs/e/doc/elib/distrib/captp/unibus.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- unibus.html 2001/05/02 01:15:01 1.7
+++ unibus.html 2001/08/20 23:53:41 1.8
@@ -78,13 +78,13 @@
<p> Note: by "private key" I mean shared secret information adequate for
a running SSL-like connection, including encryption key (eg triple DES),
MAC, and initialization vector.
- <p> In step 1, proxy b1, seeing an argument which is a proxy to a different
- remote vat, generates a new secret key K which it send over the existing
- secure channels to both VatB and VatC. It sends K to VatB <i>as</i> the
- network representation of the Carol argument of this message (step 2).
- It also sends K to VatC in a message meaning "expect someone to contact
- Carol using this K". Since this step doesn't correspond to anything on
- the existing diagram, let's call it step 2a.
+ <p> In step 1, proxy b1, seeing an argument which is a proxy to a different
+ remote vat, generates a new secret key K which it sends over the existing
+ secure channels to both VatB and VatC. It sends K to VatB <i>as</i> the
+ network representation of the Carol argument of this message (step 2).
+ It also sends K to VatC in a message meaning "expect someone to contact
+ Carol using this K". Since this step doesn't correspond to anything on
+ the existing diagram, let's call it step 2a.
<p> This private key, K, substitutes for the "VatID + SwissNumber" on the
diagram.
<p> In step 3, VatB contacts the alleged VatC according to TCP/IP hint information