W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > April 2019

Re: [webrtc-pc] Allow to import existing certificate (#2179)

From: ibsusu via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 Apr 2019 20:26:57 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-486412315-1556137616-sysbot+gh@w3.org>
My aim was to make a new session with the stored cert and then sending the required information to the torrenting peer when we've already stored the rest of the information necessary to contact them.  With regard to torrenting these certs are superfluous.  All of the files are hashed, the pieces are hashed and the peers ip address and peer id is what is used to determine whether to ignore, ban, or put them on probation.  We can pass them around with reckless abandon and not give a hoot.  Encrypting in userspace works fine as well if we need to care about it.  But right now to get around this stupid handshake problem I have to pass around natively created certs to other native peers so they can just negotiate for the peer that a browser wants to connect to.

If the browser could do this as well via an extension then we get a lot more play for design.

Does this not make sense?  Have I forgotten some detail?

-- 
GitHub Notification of comment by ibsusu
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2179#issuecomment-486412315 using your GitHub account
Received on Wednesday, 24 April 2019 20:26:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:15:03 UTC