W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2017

[webrtc-pc] RTCCertificate Interface should (or should not) be backed up.

From: Tim Panton via GitHub <sysbot+gh@w3.org>
Date: Mon, 11 Dec 2017 09:38:45 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-280950242-1512985123-sysbot+gh@w3.org>
steely-glint has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCCertificate Interface should (or should not) be backed up. ==
in "4.10.2 RTCCertificate Interface"
we say 
"The RTCCertificate object can be stored and retrieved from persistent storage by an application. " 
It isn't clear if this should be backed when the rest of a browser is backed up or indeed sync'd (i.e. bookmarks etc).

In contrast to the rest of localStorage, there is no mechanism for a service to access the privateKeys - so no way for them to be backed up and restored (e.g. in case of a phone being immersed in water).

What is the intended behaviour?

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1694 using your GitHub account
Received on Monday, 11 December 2017 09:38:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 11 December 2017 09:38:48 UTC