|
1 | | -Chapter 4. Key Predistribution |
| 1 | +Chapter 4. Key Distribution |
2 | 2 | =============================== |
3 | 3 |
|
4 | 4 | We have seen that ciphers and authentication codes are parameterized |
@@ -32,13 +32,19 @@ session keys and predistributed keys: |
32 | 32 | bulk traffic for confidentiality. |
33 | 33 |
|
34 | 34 | 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. |
42 | 48 |
|
43 | 49 | 4.1 Predistribution of Public Keys |
44 | 50 | ------------------------------------ |
@@ -280,7 +286,7 @@ certificate when it is issued. Thus, we can limit the length of time |
280 | 286 | that a revoked certificate needs to stay on a CRL. As soon as its |
281 | 287 | original expiration date is passed, it can be removed from the CRL. |
282 | 288 |
|
283 | | -4.2 Predistribution of Secret Keys |
| 289 | +4.2 Distribution of Secret Keys |
284 | 290 | ------------------------------------ |
285 | 291 |
|
286 | 292 | Secret key ciphers present a bootstrapping problem: how do you |
|
0 commit comments