Firefox 66.0.5 and 60.6.3 ESR update. Disable some APIs when accessing without HTTPS

Hot on the heels of additional corrective releases published Firefox 66.0.5 ΠΈ 60.6.3 ESRs, which continued work on restoring add-ons disabled due to expired intermediate certificate.

In particular, resolved problem with updating the intermediate certificate in case of setting a master password, through which access to the database of saved accounts is controlled. Since replacing the certificate requires that the master password be entered as
detour To solve the problem, you can perform any action that requires entering a master password (for example, request a view of saved passwords or initiate auto-completion of a remembered login form).

In addition, there are several recent developments related to Firefox:

  • In Firefox 67 and 68 it's decided expand the number of API calls that will be available only when the page is opened in a protected context (Secure Context), i.e. when opened over HTTPS, through localhost, or from a local file. In Firefox 67, for pages opened outside of a secure context, will be banned displaying system notifications via API Notificationsdisplayed outside the browser window. In Firefox 68, insecure calls will block call requests getUserMedia() to access media sources (such as the camera and microphone). It should be noted that these restrictions are already apply since Chrome 62 and 47.
  • Π’ night assembly, on the basis of which the release of Firefox 68 is formed, replaced address bar implementation. Awesome Bar was replaced by Quantum Bar. From the user's point of view, with a few exceptions, everything remains as before, but the insides completely redone and the code has been rewritten to replace XUL/XBL with the standard Web API.

    The new implementation greatly simplifies the process of extending functionality (supports the creation of add-ons in the WebExtensions format), removes hard bindings to browser subsystems, makes it easy to connect new data sources, has higher performance and responsiveness of the interface.
    Of the noticeable changes in behavior, only the need to use Shift+Del or Shift+BackSpace combinations (previously worked without Shift) is noted to remove browsing history entries from the result of the prompt displayed at the start of typing.

  • Has begun the process of replacing the classic edition of Firefox for Android with a new browser for mobile devices developed as part of the project Fenix and using the GeckoView engine and a set of libraries Mozilla Android Components, which are already used to build browsers Firefox Focus ΠΈ Firefox lite. GeckoView is a variant of the Gecko engine that is packaged as a standalone library that can be updated independently, while Android Components includes libraries with generic components that provide tabs, input completion, search suggestions, and other browser features.

    Firefox 68 will be the last release that will form an update to Firefox Classic for Android. Starting with Firefox 69 due September 3rd, new releases of Firefox for Android will not be released, and fixes will be delivered as updates to the Firefox 68 ESR branch. Currently, Fenix
    is in preparation for the start of beta testing and still lags behind Firefox for Android in terms of functionality. The first stable release of Fenix ​​1.0 is expected in June, and the Fenix ​​2.0 browser is scheduled to be released before mid-August.

Source: opennet.ru

Add a comment