Kurt Roeckx <k...@roeckx.be> writes: >The extensions are not related to TLS, but are extentions / add-ons of the >browser itself. Firefox dropped support for the old way of doing extensions >in version 57. They also added the WebExtensions API that is also implemented >in other browsers. This required major rewrites of the extensions, and some >were never changed to work with the new API.
As I understand it (E&OE), the flow was that a bunch of SCADA stuff used browser extensions, presumably to talk things like IEC 61850. When the existing extensions broke, there was a general exodus from Firefox to Chrome, however when Chrome broke at the TLS level there was indecision about what to do. There are also IE plugins, I assume the advice going forwards will be to use IE. (I have no idea about the prevalence of IE vs. others, but since it's the default browser for Windows I assume this will be the easiest/recommended path fowards, and until Windows 10 MS had a long history of being excruciatingly careful about backwards compatibility so it seems the safest bet). Peter. _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
