- From: Mark Foltz \(Google\) via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 May 2019 22:02:20 +0000
- To: public-webscreens@w3.org
These are some interesting thoughts, thank you for noting them. Trust of a name-to-key binding in the 1.0 spec happens as part of the mutual authentication handshake outlined in the spec, which accepts the current friendly name offered by the device if it is able to prove ownership of the associated certificate. If the name or certificate changes, then the binding is flagged or forgotten. Sections 3, 4, and 8.5.2 of the spec discuss this; we still have some details to work through. Using a separate, trusted signing certificate for name-to-key binding is also possible, but not currently part of the 1.0 spec. I feel it is something we should look at as a future enhancement. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/issues/113#issuecomment-488848374 using your GitHub account
Received on Thursday, 2 May 2019 22:02:21 UTC