Skip to content

change title and cover shared secrets #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
llpeterson merged 1 commit into from
Jul 31, 2025
Merged

change title and cover shared secrets #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 15 additions & 9 deletions key-distro.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Chapter 4. Key Predistribution
Chapter 4. Key Distribution
===============================

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

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

We henceforth use “Alice” and “Bob” to designate participants, as is
common in the cryptography literature. Bear in mind that although we
tend to refer to participants in anthropomorphic terms, we are more
frequently concerned with the communication between software or
hardware entities such as clients and servers that often have no
direct relationship with any particular person.

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

4.2 Predistribution of Secret Keys
4.2 Distribution of Secret Keys
------------------------------------

Secret key ciphers present a bootstrapping problem: how do you
Expand Down