Skip to content

Commit da3a0e0

Browse files
authored
Merge pull request #27 from SystemsApproach/keydistro
change title and cover shared secrets
2 parents 0a312c5 + 4bbc028 commit da3a0e0

File tree

1 file changed

+15
-9
lines changed

1 file changed

+15
-9
lines changed

key-distro.rst

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Chapter 4. Key Predistribution
1+
Chapter 4. Key Distribution
22
===============================
33

44
We have seen that ciphers and authentication codes are parameterized
@@ -32,13 +32,19 @@ session keys and predistributed keys:
3232
bulk traffic for confidentiality.
3333

3434
This chapter explains how predistributed keys are distributed, and then
35-
explains how session keys are subsequently established. We
36-
henceforth use “Alice” and “Bob” to designate participants, as is common
37-
in the cryptography literature. Bear in mind that although we tend to
38-
refer to participants in anthropomorphic terms, we are more frequently
39-
concerned with the communication between software or hardware entities
40-
such as clients and servers that often have no direct relationship with
41-
any particular person.
35+
explains how session keys are subsequently established. Note that
36+
session keys are a particular example of a shared secret, and in some cases
37+
there is a need for more than just a simple session key. In such cases we
38+
use the more general terminology of "shared secret establishment"
39+
rather than "session key distribution". The basic principles are the
40+
same.
41+
42+
We henceforth use “Alice” and “Bob” to designate participants, as is
43+
common in the cryptography literature. Bear in mind that although we
44+
tend to refer to participants in anthropomorphic terms, we are more
45+
frequently concerned with the communication between software or
46+
hardware entities such as clients and servers that often have no
47+
direct relationship with any particular person.
4248

4349
4.1 Predistribution of Public Keys
4450
------------------------------------
@@ -280,7 +286,7 @@ certificate when it is issued. Thus, we can limit the length of time
280286
that a revoked certificate needs to stay on a CRL. As soon as its
281287
original expiration date is passed, it can be removed from the CRL.
282288

283-
4.2 Predistribution of Secret Keys
289+
4.2 Distribution of Secret Keys
284290
------------------------------------
285291

286292
Secret key ciphers present a bootstrapping problem: how do you

0 commit comments

Comments
 (0)