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.

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

Handling of KeyingMaterial internal slot #1802

Merged
merged 1 commit into from
Mar 15, 2018
Merged
Changes from all commits
Commits
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
20 changes: 12 additions & 8 deletions webrtc.html
Original file line number Diff line number Diff line change
Expand Up @@ -4672,14 +4672,18 @@ <h2>Methods</h2>
</section>
</div>
<p>For the purposes of this API, the <a>[[\Certificate]]</a> slot
contains unstructured binary data.</p>
<p>Note that an <code>RTCCertificate</code> might not directly hold
private keying material, this might be stored in a secure module.</p>
<p>The <code>RTCCertificate</code> object can be stored and retrieved
from persistent storage by an application. When a <a>user agent</a> is
required to obtain a structured clone [[!HTML51]] of an
<code>RTCCertificate</code> object, it performs the following
steps:</p>
contains unstructured binary data. No mechanism is provided for
applications to access the <a>[[\KeyingMaterial]]</a> internal slot.
Implementations MUST support applications storing and retrieving
<code>RTCCertificate</code> objects from persistent storage.
In implementations where an <code>RTCCertificate</code> might not
directly hold private keying material (it might be stored in a
secure module), a reference to the private key can be held in
the <a>[[\KeyingMaterial]]</a> internal slot, allowing the
private key to be stored and used.</p>
<p>When a <a>user agent</a> is required to obtain a structured
clone [[!HTML51]] of an <code>RTCCertificate</code> object,
it performs the following steps:</p>
<ol>
<li>Let <var>input</var> and <var>memory</var> be the corresponding
inputs defined by the internal structured cloning algorithm, where
Expand Down