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

Re: [webrtc-pc] What happens if cert expires mid call ?

From: Martin Thomson via GitHub <sysbot+gh@w3.org>
Date: Thu, 01 Jun 2017 12:54:01 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-305484300-1496321639-sysbot+gh@w3.org>
Answer: nothing.  It's just too hard to worry about these things.  Life is too short.

(FWIW, these little policy things are usually left to the endpoints to sort out.  In HTTP-land, I don't think that anyone kills connection at this point, but they might and we probably will never see it outside of an artificial test.  That test would be highly proprietary.  That's because the rules by which a user agent determines that a certificate is "acceptable" vary considerably.  There are some common things - a great many even - but the edges aren't always clear.  I realize that this makes some people unhappy, but here's a free tip: don't let your certificates expire.)

-- 
GitHub Notification of comment by martinthomson
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1318#issuecomment-305484300 using your GitHub account
Received on Thursday, 1 June 2017 12:54:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:43 UTC