Correlation does not imply causation. And in this case, it seems like there are pretty good candidates for the common cause. And the article even recognises that - the headline is clickbait.
Not for ever - they are working on a method of doing bridge-based WebRTC which is nevertheless end-to-end secure - see https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fdatatracker.ietf.org%2Fw... . AIUI, the way it works is that it established point-to-point encrypted tunnels between the endpoints for key distribution so the bridge isn't able to decrypt the data even if it wanted to, and yet, you don't need N->N transmission of streams.
Gerv
WebRTC-based services, in the form of e.g. https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fmeet.jit.si%2F, are end-to-end secure and decentralised. Not sure if Windows Phone has any browser which supports WebRTC, though.
web.skype.com lets me log in using Firefox, no problem, so presumably it works there as well.
Gerv
It a load of rubbish from the original author. There's no reason whatsoever that loss of this data would cause problems in IE or Edge. Removing roots from MS's program doesn't happen without human input.
"What I don't understand (and maybe because I haven't looked too hard) is what "Old POS terminals" have to do with Mozilla."
The certificates they are using chain up to publicly-trusted roots, and so are covered by Mozilla's policies. In 20-year hindsight, that was a bad idea, but it was a decision taken a long time ago.
Er, it's a wiki. Add it.
The code for the DRM module Firefox uses is not part of the Firefox build system, but is downloaded at runtime. This can be done whether it's a Firefox built by Mozilla or not. So the DRM question has no bearing on whether you can call your version Firefox or not.
This series of blog posts: http://blog.gerv.net/2010/01/p... explains why Mozilla doesn't let just anyone call their modified version "Firefox".
Gerv
The bug is unfixed for philosophical reasons, not because it's hard to fix. The Bugzilla developers feel history should be immutable.
And there has been no rewrite into another language since that bug was filed; Bugzilla as released by Mozilla has always been in Perl.
Gerv
There was no issue with the Bugzilla software here; the problem was that a user reused their password on another site, which suffered a breach.
Gerv
we could have lawful access... that we're prohibited from getting because of a company's technological choices.
Now you know how the public feels when they want to make fair use of some video on a DVD or Bluray.
CAs normally issue certs with 1-year validity. As they may not expire later than 2015-11-01, CAs will mostly stop issuing them on 2014-11-01. I guess you could ask them to cut a cert with a special, shorter lifetime but that would be hassle (and therefore extra cost).
Justin: sadly not so, 3.6.21 is not released yet. It will be in the next 48 hours, though.
We do care about bug reports, and we try and appear we care about bug reports - both by saying that we care, and trying to handle them. But Tyler is suggesting that our failure to handle all of them means that it might appear that our actions speak louder than our words.
If you want to help the two match up, do get involved with Mozilla
How many hardware guys does it take to change a light bulb? "Well the diagnostics say it's fine buddy, so it's a software problem."
