Skip to content

For Ben #21

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

Closed
martinthomson wants to merge 1 commit into from
Closed

For Ben #21

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
10 changes: 5 additions & 5 deletions draft-ietf-webpush-encryption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,11 +94,11 @@ messages are encrypted using an encrypted content encoding {{!RFC8188}}. This
document describes how this content encoding is applied and describes a
recommended key management scheme.

Multiple users of Web Push often share a central agent that aggregates push
functionality. This agent can enforce the use of this encryption scheme by
applications that use push messaging. An agent that only delivers messages
that are properly encrypted strongly encourages the end-to-end protection of
messages.
Multiple users of Web Push at the same user agent often share a central agent
that aggregates push functionality. This agent can enforce the use of this
encryption scheme by applications that use push messaging. An agent that only
delivers messages that are properly encrypted strongly encourages the end-to-end
protection of messages.

A web browser that implements the Web Push API {{API}} can enforce the use of
encryption by forwarding only those messages that were properly encrypted.
Expand Down