The larger the code base the harder it is to secure, or in other words, the more things that can go wrong, the more things will go wrong. Pale Moon has no such difficulties adapting relevant security issues, and if you peruse the release notes, you will notice that the majority of Firefox security issues are “not applicable” to Pale Moon. This is the problem with not being an actual hard fork of Firefox. Hopefully we will see other contributors chipping in to the project to ease the burden. Kontos has done a commendable job in maintaining Waterfox for over 10 years, and it can't be easy to work on two projects at the same time. That is not a very reassuring message, although it is quite understandable and the transparency is appreciated. Waterfox Classic will warn the user that the browser could be vulnerable to multiple security issues, and it is up to the user to decide whether to proceed to user it or not. These changes are expected to go live this week. The announcement also says that Waterfox Classic will have its own page on the official site, this is something which has bothered some users, as the lone mention of it, has been the link to the releases page, from which you can download the browser. A list of unpatched security issues will be made available on the browser's website. The developer says that Waterfox Classic's future will rely on contributions, by which he probably means what he previously mentioned, about porting security fixes from Firefox ESR. And since it is no longer tied with G4, issues won't be closed because of complications/incompatibilities with the modern version. Now that Waterfox Classic has its own Github repository, users will be able to track and report issues related specifically to it. But more importantly, this will improve the development process of the browser, because previously, issues related to both versions were tackled together.
Firstly, users who relied on it will get new versions. This is a welcome move for multiple reasons.
0 kommentar(er)
