Skip to content
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

Jump to bottom

Fix examples #259

Closed
wants to merge 3 commits into from
Closed

Fix examples #259

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6c26164
Fix examples
martinthomson Nov 2, 2016
d53076e
Add intermediate values, expand explanation of examples
martinthomson Nov 2, 2016
4cd62c9
More expansion on the examples
martinthomson Nov 2, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 10 additions & 8 deletions draft-ietf-httpbis-encryption-encoding.md
View file
Open in desktop
Expand Up @@ -361,9 +361,10 @@ wrapping is added to fit formatting constraints.

## Encryption of a Response {#explicit}

Here, a successful HTTP GET response has been encrypted using input keying
material that is identified by an empty string (that is, the "keyid" field is
zero octets in length).
Here, a successful HTTP GET response has been encrypted. This uses a record
size of 4096 and the minimum of 2 octets of padding, so only a partial record is
present. The input keying material is identified by an empty string (that is,
the "keyid" field in the header is zero octets in length).

The encrypted data in this example is the UTF-8 encoded string "I am the
walrus". The input keying material is included in the Crypto-Key header field.
Expand Down Expand Up @@ -398,11 +399,12 @@ plaintext = AABJIGFtIHRoZSB3YWxydXM

## Encryption with Multiple Records

This example shows the same encrypted message, but split into records of 10
octets each (that is, the "rs" field in the header is 10). The first record
includes a single additional octet of padding, which causes the end of the
content to align with a record boundary, forcing the creation of a third record
that contains only padding.
This example shows the same message, but the plaintext is split into records of
10 octets each (that is, the "rs" field in the header is 10). The first record
includes a single additional octet of padding. This means that there are 7
octets of message in the first record, and 8 in the second. This causes the end
of the content to align with a record boundary, forcing the creation of a third
record that contains only two octets of padding.

~~~ example
HTTP/1.1 200 OK
Expand Down