Basilisk 2023.01.07

Aller sur le site officiel

Basilisk est un navigateur internet "laboratoire", c'est-à-dire, que les développeurs le considère comme toujours en phase "bêta". Originellement crée par les développeurs de MoonChild Productions, éditeur du navigateur Pale Moon, il était destiné à tester certaines fonctions avant intégration à Pale Moon. Désormais, depuis août 2022, Basilisk vole de ses propres ailes grâce à une nouvelle équipe.

Toujours clone de Firefox et basé sur le moteur Goanna (fork de Gecko), cette nouvelle équipe continuera à développer le code (basé sur XUL) abandonné par l'équipe de Mozilla lors du basculement de Firefox 56 à 57 tout en le modernisant.

De ce fait, Basilisk est désormais un navigateur totalement indépendant et suit donc son propre rythme de mise à jour. Il est cependant disponible que sur Windows (à partir de Windows 7) et Linux. Une version compatible pour macOS ARM (M1/M2) est en préparation...

Basilisk
Version actuelle : 2023.01.07 - Voir les extensions disponibles
[🇺🇸] : Windows 32 bits, 64 bits | Linux

Notes de version de Basilisk 2023.01.07 (07/01/2023)

This is a major development, bugfix and security release.

  • Added support for the JPEG-XL image format.
  • Implemented regular expressions lookaround/lookbehind.
  • Aligned CORS header parsing with the updated spec. See implementation notes.
  • We no longer fire keypress events for non-printable keys. See implementation notes.
  • Added support for MacOS 13 "Ventura" in the platform, primarily benefitting White Star.
  • Fixed potentially problematic thread locking code on *nix platforms.
  • Fixed some small issues in the display and operation of the Web Developer tools.
  • Removed unused but performance-impacting panning and tab animation measuring code. (telemetry leftovers)
  • Improved code for SunOS builds.
  • Updated Internationalization data for time zones.
  • Fixed a buffer overflow for Mac builds.
  • Fixed an issue with plugins not receiving keypress events properly.
  • Added some extra sanity checks to our zip/jar/xpi reader to avoid issues with corrupt archives.
  • Aligned cookie checks with RFC 6265 bis. See implementation notes.
  • Removed obsolete code in Windows widgets that could cause potential issues with long paths and file names on supported versions.
  • Fixed several crashes.
  • Security issues addressed: CVE-2022-45411, CVE-2022-46876, CVE-2022-46874 and several others that do not have a CVE number
  • UXP Mozilla security patch summary: 6 fixed, 1 DiD, 1 deferred, 45 not applicable.

Implementation notes

  • RFC 6265 has been worked on with draft changes describing how cookies are actually being handled in the real world, in the bis versions of the RFC. While these changes have not yet been finalized, browsers in general do adhere to the latest available bis version of this RFC. Specifically, the long-standing exceptions for cookie names and values have been formalized, e.g. having quoted values. Our behavior has changed in that we now once again accept Tab characters (0x09) which is the one excluded control character from the range that is otherwise forbidden. We also no longer apply these checks exclusively to those in http headers, and any way of setting cookies must now adhere to the valid range. Cookies that fail these range checks for valid characters will be ignored.
  • CORS support has been updated to the current spec. Most importantly, Basilisk now accepts wildcard entries ("*") for the CORS statements Access-Control-Expose-Headers, Access-Control-Allow-Headers and Access-Control-Allow-Method. Note that wildcards are ignored (according to the spec) when credentials are passed.
  • Basilisk will no longer fire the keypress events in content when the key pressed is a non-printable key. This is in response to issues where webmasters would use rudimentary and naïve input-restricting scripts in onkeypress handlers that would not take into account editing keys or navigation keys, causing issues for users trying to enter data into forms (and e.g. finding they could no longer use backspace, cursor keys or tab). This aligns our behavior with other browsers for web compatibility, although it should be considered a website error expecting not all keypresses to be intercepted in keypress events.
Notes de versions complètes de Basilisk