Note however that there is no way to bypass this change in Firefox's policy. There is a page in the Security Team's knowledge base that details this issue a little more, or at least, provides a timeline for all the events related to this.
Note however that there is no way to bypass this change in Firefox's policy. There is a page in the Security Team's knowledge base that details this issue a little more, or at least, provides a timeline for all the events related to this.