SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here a more detailed description and scripts for building the newly updated Basilisk browser (basilisk-2021.12.14) for 32 and probably also 64bit Slackware.
The build folder must contain:
all to be "lifted" from Khronosschotty's 2019.09.03 SlackBuild / his basilisk.tar.gz.
Also the 2021.12.14 source published on PaleMoon's website must be present:
basilisk-2021.12.14-source.tar.xz
plus the files:
basiliskrepack.sh
basilisk.SlackBuild
from below.
First repacking the source with ./basiliskrepack.sh and then building with ./basilisk.SlackBuild (as SU) should result in a nice and up to date Basilisk for 32bit.
It looks like Basilisk may be history, according to this post by Moonchild:
Quote:
...As such, I may be retiring Basilisk and stop development on it altogether, or potentially split it off to do something else with it -- I'm not sure yet. If people are genuinely interested in seeing it continue in its current form, I'll consider someone taking it over, too. Contact me in that case.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,153
Original Poster
Rep:
Quote:
Implementation notes:
Despite being removed in 29.4.0 and 29.4.2, the long-since deprecated FUEL abstraction functions inside Pale Moon have been restored again after considerable blowback from the community and lack of effort to fix afflicted extensions. It was decided to just restore this indefinitely in the end, since it serves no-one to have users be forced to do without or stay on insecure versions of the browser for something nobody seems to want to address in the extension ecosystem. A more in-depth announcement about a change in direction tying in with this note can be found on the forum.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Aw, man...Basilisk is a damn fine browser. Really, really fast compared to any others I use/used...at least starting up it's the fastest. I too would surely hate to see it go by the wayside. <sigh>
I guess I'll see if Palemoon works as I want it to. I'm going to have to start digging for new/obscure/unheard of/high privacy browsers again it seems. Meh
basilisk-bin runs very well on my Slackware 64 Current + Multilib System, even after updating his basilisk-bin.SlackBuild for the most up-to-date basilisk-latest.linux64.tar.xz blob ( VERSION="52.9" ; BUILD="2021.12.14" )
Last edited by kjhambrick; 12-21-2021 at 04:14 AM.
Reason: add thanks to khronosschoty for basilisk-bin.SlackBuild
kgha and JayBird in november discussed JustOff's polyfill.xpi extension mitigating Basilisk's poor handling of GitHub.
Installing the extension into Basilisk directly from GitHub did not succeed on the Basilisk build from source on my system erroring "not compatible with Basilisk 52.9.0".
Circumventing problems with .xpi extensions may from and then, as many know, be possible if editing the content in the extension by renaming it to .zip, unzipping and editing e.g the install.rdf file before zipping and renaming in reverse, and afterwards installing the modified .xpi using "install add-on from file" from the "extensions" drop down list.
In the polyfill.xpi case replace the line in install.rdf:
<em:minVersion>52.9.2021.11.06</em:minVersion>
with
<em:minVersion>52.9.0</em:minVersion>
Probably this problem with JustOff's extension only apply to home-compiled Basilisk's / the date of build, i dunno!
kgha and JayBird in november discussed JustOff's polyfill.xpi extension mitigating Basilisk's poor handling of GitHub.
Installing the extension into Basilisk directly from GitHub did not succeed on the Basilisk build from source on my system erroring "not compatible with Basilisk 52.9.0".
Circumventing problems with .xpi extensions may from and then, as many know, be possible if editing the content in the extension by renaming it to .zip, unzipping and editing e.g the install.rdf file before zipping and renaming in reverse, and afterwards installing the modified .xpi using "install add-on from file" from the "extensions" drop down list.
In the polyfill.xpi case replace the line in install.rdf:
<em:minVersion>52.9.2021.11.06</em:minVersion>
with
<em:minVersion>52.9.0</em:minVersion>
Probably this problem with JustOff's extension only apply to home-compiled Basilisk's / the date of build, i dunno!
or you could change it to something like <em:minVersion>52.9.*</em:minVersion>
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,153
Original Poster
Rep:
The End.
The release notes explain it.
Quote:
v2022.01.27 Published 2022-01-27
This is a security update. Important: This is the final public release of Basilisk from the original developer. As such, it comes without an internal updater and will not check for future updates to the application.
To remain updated and secure, it is recommended at this point that you look for a different web browser like Pale Moon to continue browsing in a safe and secure manner.
Be mindful of hacks: There are currently no people eligible to continue Basilisk as a product under the Basilisk name. If you see any future updates claiming/pretending to be official Basilisk or an official continuation, they are most likely scams and should not be trusted with your browsing.
Improved application library loading security. DiD
Fixed an issue in JavaScript serialization. DiD
Fixed a potential out-of-bounds issue in IndexedDB. DiD
Fixed a potential issue in widget data handling code. DiD
Fixed potentially exploitable crashes in handling truncated/corrupt media files or streams.
Fixed an issue in the DOM FileReader code.
Updated NSS to 3.52.3 to address a security issue.
Updated the installer to fix a rights elevation issue.
Fixed the following security issues: CVE-2022-22736, CVE-2022-22741, CVE-2021-4140, CVE-2022-22746, CVE-2022-22744 and CVE-2022-22747.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,086
Rep:
A pity.
Apparently Mr. Moonchild has offered to leave Basilisk to some other to maintain (for a fee), but he's a bit particular about who might be deserving such an honour, see https://forum.palemoon.org/viewtopic.php?f=61&t=27722
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
I'm pretty bummed about it. It's fast, it's private, it's non-intrusive, it's all the good stuff. <sigh>...I guess after a while I'll have to flip a coin or draw from a hat whether to use PaleMoon, Firefox, or Konqueror (back in the KDE 3 days I *loved* Konqueror for my web browser, then it got so bloated during KDE 4 that I hated it. Hopefully in Plasma it'll kick ass again).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.