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

Clarify encryption key lifetime and intention #224

Merged
merged 1 commit into from
Nov 18, 2016
Merged

Clarify encryption key lifetime and intention #224

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: 9 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -349,6 +349,12 @@ <h2>
with a <a>service worker registration</a> and a <a>service worker registration</a> has at
most one <a>push subscription</a>.
</p>
<p>
A <a>push subscription</a> has internal slots for a P-256 <a>ECDH</a> key pair and an
authentication secret in accordance with [[!WEBPUSH-ENCRYPTION]]. These slots MUST be
populated when creating the <a>push subscription</a>, and MUST remain constant for its
lifetime.
</p>
<p>
When a <a>push subscription</a> is <dfn data-lt=
"deactivated|deactivate">deactivated</dfn>, both the <a>user agent</a> and the <a>push
Expand Down Expand Up @@ -845,7 +851,9 @@ <h2>
</li>
</ol>
<p>
Keys named <code><a>p256dh</a></code> and <code><a>auth</a></code> MUST be supported.
Keys named <code><a>p256dh</a></code> and <code><a>auth</a></code> MUST be supported, and
their values MUST correspond to those necessary for the user agent to decrypt received push
messages in accordance with [[!WEBPUSH-ENCRYPTION]].
</p>
<p>
The <code><dfn id=
Expand Down