LibreWolf AppImage 64-bit Only: Privacy Hardened Firefox

[mikewalsh]

Now then, gang.

After much head-scratching, here is the new 'portable' version of 64-bit LibreWolf.

Initially, I thought this was going to be a "no-go". The last few LibreWolf AppImages that I've tried have, without fail, told me that they can't mount.....because Puppy's version of fusermount is WAY too old. From this, I take away the fact that these have probably been built by somebody who is running a 'bleeding-edge', rolling-release distro like Arch, which is constantly upgrading to the very newest of everything, all the time. Even Fossapup is nearly a year-and-a-half old now; in rolling-release terms, this is a lifetime!

But, there's 'workarounds' for pretty much everything, IF you put your considering cap on. Accordingly, I've run the AppImage with the

Code: Select all

--appimage-extract

....."-switch", which unzips it. And what you're effectively left with is a ROX-app. Which runs fine.

---

I've employed the techniques I've been refining with my recent rash of 'portable' applications. Instead of creating, and using, the profile directly within the portable itself, the profile directory is created inside the portable, and THEN it's sym-linked out to where the application expects to find it. At first run, the sym-linked directory is populated with all the profile stuff, though in reality it's actually writing direct to the portable anyway....

The sym-linked .librewolf profile directory sits in /root (the user's $HOME directory, in Puppy's case). However, LibreWolf still runs-as-spot. Immediately prior to launch, everything that needs it is chowned to spot:spot permissions, EVEN the sym-linked .librewolf directory in /root......which at shutdown, is deleted again.

Suffice it to say, it all runs very sweetly indeed.

---

I'm NOT going to be building this on a regular basis. I won't NEED to. You, the user, can easily upgrade this yourself.

• Keep an eye on

  https://gitlab.com/librewolf-community/ ... -/releases

  This is the download location for the AppImages, which appears to be the sole package format these are released in. Download the current version, and extract it to obtain the AppImage itself.

• In the directory where the new AppImage is located, open a terminal (rt-clk->Windows->Terminal here). Run the following command:-

  Code: Select all

  ./xxxxxxxxx.AppImage --appimage-extract

  .....where xxxxxxxxx is the name of the AppImage exactly as it is written.

• This will unzip the AppImage, and leave a directory called "squashfs-root". This is basically a ROX-app; clicking on this will actually fire it up. However; what you want to do is to re-name this to the same as the one already inside the portable, so rename it to "LibreWolf64". Then, just swap this with the one in the portable.

• You have now upgraded LibreWolf to the new version, and can continue to use it with your existing profile.

Easy, isn't it?

---

The current portable can be found here:-

https://mega.nz/folder/bTJWCQSb#TXwTjaoWJwe_YRaDXkPB-w

Have fun!

Mike.

[geo_c]

now; in rolling-release terms, this is a lifetime!

But, there's 'workarounds' for pretty much everything, IF you put your considering cap on. Accordingly, I've run the AppImage with the

Code: Select all

--appimage-extract

....."-switch", which unzips it. And what you're effectively left with is a ROX-app. Which runs fine.

-----------------------------------------------------------

• In the directory where the new AppImage is located, open a terminal (rt-clk->Windows->Terminal here). Run the following command:-

  Code: Select all

  ./xxxxxxxxx.AppImage --appimage-extract

  .....where xxxxxxxxx is the name of the AppImage exactly as it is written.

• You have now upgraded LibreWolf to the new version, and can continue to use it with your existing profile.

Mike.

Hmm @mikewalsh I just downloaded the appimage and made it executable. Sure I didn't use my old profile, but it did indeed fire up and I'm using it now after adjusting it to my taste. Are you saying it might just quit working at some point?

@geo_c

[mikewalsh]

@geo_c :-

Very doubtful it'll simply quit working; I've never known any browser to do that.....unless the user makes some major change to his/her system which removes stuff the browser depends on.

No, some people just like to always be using the very newest version of everything, regardless of whether it's actually necessary. Where browsers - or anything internet-facing - are concerned, I try to keep on top of things as much of the time as I can. With many other items, I'm nowhere near as bothered.

The 'net is where most of your "nasties" originate. No sense inviting trouble when it CAN be avoided.

Mike.

[xenial]

I tried this on fossapup64.Not impressed frankly.
Go to a video site and the laptop attempts to take off..Bad reaction to my system i guess.

I would assume most of the privacy achieved here can be done tweaking normal firefox.

Browser for the super-paranoid among us.
There is a fundamental difference between actual malicious spyware and legitimate telemetry.

I never thought i would ever say this but google chrome is the best performer at the moment and google probably has me profiled anyway so if it works bloody leave it alone.

[geo_c]

I tried this on fossapup64.Not impressed frankly.
Go to a video site and the laptop attempts to take off..Bad reaction to my system i guess.

I would assume most of the privacy achieved here can be done tweaking normal firefox.

Browser for the super-paranoid among us.
There is a fundamental difference between actual malicious spyware and legitimate telemetry.

I never thought i would ever say this but google chrome is the best performer at the moment and google probably has me profiled anyway so if it works bloody leave it alone.

Interesting about the video. I don't watch movies, or netflix, or any of that stuff, but everything plays quite well for me, like long youtube stuff. I like Libre, but I bounce back and forth between it and ungoogled chromium. Everyone complains about Libre's lack of window position/size memory -- yeah, that's pretty annoying. But, for me, I split a secondary screen and it opens to exactly the width I want, so that works.

I'm still not sure if Libre 'phones home' through Mozilla, because it works with their site. However it seems like maybe it doesn't. I'm sure @mikewalsh knows. Anyway, I like Libre. I use it for everything, a document viewer, a file browser, a web browser, a media player. And it looks good when tweaked.

[xenial]

It may have been just a bad install but i do like the browser and may try again.I downloaded the appimage and just executed..Youtube locked the entire os up so not sure what could be happening there.
For ordinary browsing it appears snappy and consistent.

[geo_c]

It may have been just a bad install but i do like the browser and may try again.I downloaded the appimage and just executed..Youtube locked the entire os up so not sure what could be happening there.
For ordinary browsing it appears snappy and consistent.

I feel like Fossapup has some issues with locking up during high display loads. It happens when multiple graphics applications are active, and for me just occasionally, maybe every couple weeks, sometime a month. I notice it when various browsers (and it doesn't seem to matter which) are active, and especially if running a desktop switcher like JWM desk, or even if using a photo editor, video editor, or zoom meetings. Seems like the wrong combination of graphics calls, and the OS locks. I'm using the latest Libre appimage for a week or so, and it hasn't had any issues.

[Feek]

I would assume most of the privacy achieved here can be done tweaking normal firefox.

Hi,
in Fossapup I use relatively long time normal Firefox (installed from quickpet) with settings recommended by Sun Knudsen:

https://sunknudsen.com/privacy-guides/h ... references

I have two profiles, one of them is strict. It works very well for me although the setup took some time

[xenial]

Been tinkering with this one for the past few days.
On my limited computer.((for the time being))the memory usage seemed rather high for my liking and tends to keep creeping up as you browse further.

i find chrome/chromium browsers have better memory management than gecko based ones.i don't see anything here which i couldn't do myself within standard firefox like implementing prefs etc.

[mikeslr]

Download the AppImage, currently, from https://librewolf.net/installation/linux/
Extract it, for example Right-Click and select UExtract. By default that will create, adjacent to the AppImage, itself, a folder bearing the name of the AppImage version but ending in “.extracted”.

With Rox as file-manager the above described folder is recognized as a ‘rox-app’. If you click it LibreWolf will start (if your OS supports it OOTB). You can Right-Click that folder and from the pop-up menu select Rename. Give it any name you want. I chose Librewolf98 so as to keep track of what version I have. [AFAIK it can not be updated]. You can then move the folder where ever you want.

Under Fossapup64 both the AppImage and the extracted folder ran OOTB, including the ability to play youtube videos with sound. But like (inherited from) firefox, AS-IS, those will store customizations and settings in your ‘Home Folder” and more significantly also write cache files there. Under frugal Puppys, your Home Folder is /root, and "/root is in RAM". As cache from the web can increase in size rapidly, that can impact the responsiveness of your operating system, even resulting in system crash. Further complication arise as the contents of /root will be written to your SaveFile/Folder when you execute a Save and thus be copied back into RAM on boot-up. This is why both fredx181 and MikeWalsh built their portables so that profiles (configurations, bookmarks, and addons) and cache would be written instead to the portable’s own folder.*

I don’t have either fred’s or Mike’s programming skills. So I flinched their work to produce the attached “wolf-pup2” script.

wolf-pup2.gz

(1.52 KiB) Downloaded 58 times

REMOVE the false ‘.gz’ ending and drop it into your folder. Left-Clicking it will start LibreWolf.

Although folders will still be created in /root and /root/.cache they will not be populated. Rather, LibreWolf’s own folder will be used.

The wolf-pup2 script runs LibreWolf as ‘Root’. It is likely that adding ‘run-as-spot’ to its last line will run it as spot. Something like this

exec run-as-spot "${EXEC}" "$@" -profile "$LAUNCHDIR/profile".

As noted the wolf-pup2 script is my hack. It appears to have originated as a modification of the AppRun** script which already was in the AppImage. I have no objection if someone wants to do a more professional job and create an alternative. I also won’t object if MikeWalsh takes it upon himself to publish a script to generate a menu entry to start LibreWolf from wherever the portable folder is located.
Nor will I throw a temper-tantrum if anyone figures out how to update LibreWolf without having to start-from-scratch.

-=-=-=-=-=
* Installation of the addon named "Clear Browsing Data" is still recommended by both firefox and me. And, of course, you can still configure LibreWolf to clear cache etc. on shut-down.

** If you get annoyed by LibreWolf's starting when you click its folder, then AFTER installing the wolf-pup2 script you can delete the AppRun script.

[mikeslr]

Well, it seems that the above posts resulted from my violation of two personal rules: (1) never do anything important, such as write a post, before having my 2nd cup of coffee, and (2) never start a post without having re-read the entire thread. I made both rules in recognition of my flaky memory.

Seems I was more than a spectator in the writing of the wolf-pup script, the direct parent of the wolf-pup2 script. But on a positive note, I approached LibreWolf with fresh eyes. Once the idea of running LibreWolf as spot from within a spot folder was discarded [actually not even considered], things fell into place much more easily. If you still feel it necessary to run LibreWolf as spot, MikeWalsh shows how to do it, viewtopic.php?p=19488#p19488.

And now that I'm fully awake, I've taken the time to examine the MenuAdd and Menu-Remove script Mike includes in his portables. They seem straight-forward once you realize that within the included DATA folder he includes there's an icon and a desktop file and that these are copied-to/removed-from /usr/share/pixmaps and /usr/share/applications, respectively. Sweet.

[greengeek]

I seem unable to download the file listed in first post.
Is the file still available or do I maybe have a problem accessing Mega?

[mikewalsh]

@greengeek :-

I seem unable to download the file listed in first post.
Is the file still available or do I maybe have a problem accessing Mega?

Sorry, Ian; my bad, I'm afraid. Between posting that last post and now, I'd done quite a lot of re-organising my MEGA.nz a/c. There were bound to be a few "dead" links that got overlooked.

I've re-added the correct link. Try it now.

Mike.

[greengeek]

Now then, gang.

After much head-scratching, here is the new 'portable' version of 64-bit LibreWolf.

Initially, I thought this was going to be a "no-go". The last few LibreWolf AppImages that I've tried have, without fail, told me that they can't mount.....because Puppy's version of fusermount is WAY too old. From this, I take away the fact that these have probably been built by somebody who is running a 'bleeding-edge', rolling-release distro like Arch, which is constantly upgrading to the very newest of everything, all the time. Even Fossapup is nearly a year-and-a-half old now; in rolling-release terms, this is a lifetime!

But, there's 'workarounds' for pretty much everything, IF you put your considering cap on. Accordingly, I've run the AppImage with the

Code: Select all

--appimage-extract

....."-switch", which unzips it. And what you're effectively left with is a ROX-app. Which runs fine.

---

I've employed the techniques I've been refining with my recent rash of 'portable' applications. Instead of creating, and using, the profile directly within the portable itself, the profile directory is created inside the portable, and THEN it's sym-linked out to where the application expects to find it. At first run, the sym-linked directory is populated with all the profile stuff, though in reality it's actually writing direct to the portable anyway....

The sym-linked .librewolf profile directory sits in /root (the user's $HOME directory, in Puppy's case). However, LibreWolf still runs-as-spot. Immediately prior to launch, everything that needs it is chowned to spot:spot permissions, EVEN the sym-linked .librewolf directory in /root......which at shutdown, is deleted again.

Suffice it to say, it all runs very sweetly indeed.

---

I'm NOT going to be building this on a regular basis. I won't NEED to. You, the user, can easily upgrade this yourself.

• Keep an eye on

  https://gitlab.com/librewolf-community/ ... -/releases

  This is the download location for the AppImages, which appears to be the sole package format these are released in. Download the current version, and extract it to obtain the AppImage itself.

• In the directory where the new AppImage is located, open a terminal (rt-clk->Windows->Terminal here). Run the following command:-

  Code: Select all

  ./xxxxxxxxx.AppImage --appimage-extract

  .....where xxxxxxxxx is the name of the AppImage exactly as it is written.

• This will unzip the AppImage, and leave a directory called "squashfs-root". This is basically a ROX-app; clicking on this will actually fire it up. However; what you want to do is to re-name this to the same as the one already inside the portable, so rename it to "LibreWolf64". Then, just swap this with the one in the portable.

• You have now upgraded LibreWolf to the new version, and can continue to use it with your existing profile.

Easy, isn't it?

---

The current portable can be found here:-

https://mega.nz/folder/bTJWCQSb#TXwTjaoWJwe_YRaDXkPB-w

Have fun!

Mike.

Hi Mike - firstly thanks for the new link. Got the download ok now.
I am somewhat confused though. The download is extracted as "LibreWolf-portable64" which looks like a normal roxapp or summat.
But when I click it and go inside - I then click the LAUNCH script and it doesn't run.
Manually running the LAUNCH script I get this:

Code: Select all

root# ./LAUNCH
fusermount: mount failed: Operation not permitted

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
open dir error: No such file or directory
root# 

...which sounds like what you were warning us about.

But it seems like your suggestions about extracting the appimage should not apply here - because my file is a "portable" not an "appimage" (i think..?)

So is the "portable" built in a way that should run? Or am I extracting it incorrectly? Or is the "LAUNCH" superfluous?

EDIT :" Oh - I just realised that if I click "LibreWolf64" instead of LAUNCH - it fires up.

My reason for testing this is the confusion experienced by Governor here: https://forum.puppylinux.com/viewtopic. ... 67#p133067

Anyway - hope you can understand something of my ruminations. Possible had one glass too much tonight

[greengeek]

Now then, gang.

After much head-scratching, here is the new 'portable' version of 64-bit LibreWolf.

Initially, I thought this was going to be a "no-go". The last few LibreWolf AppImages that I've tried have, without fail, told me that they can't mount.....because Puppy's version of fusermount is WAY too old. From this, I take away the fact that these have probably been built by somebody who is running a 'bleeding-edge', rolling-release distro like Arch, which is constantly upgrading to the very newest of everything, all the time. Even Fossapup is nearly a year-and-a-half old now; in rolling-release terms, this is a lifetime!

But, there's 'workarounds' for pretty much everything, IF you put your considering cap on. Accordingly, I've run the AppImage with the

Code: Select all

--appimage-extract

....."-switch", which unzips it. And what you're effectively left with is a ROX-app. Which runs fine.

---

I've employed the techniques I've been refining with my recent rash of 'portable' applications. Instead of creating, and using, the profile directly within the portable itself, the profile directory is created inside the portable, and THEN it's sym-linked out to where the application expects to find it. At first run, the sym-linked directory is populated with all the profile stuff, though in reality it's actually writing direct to the portable anyway....

The sym-linked .librewolf profile directory sits in /root (the user's $HOME directory, in Puppy's case). However, LibreWolf still runs-as-spot. Immediately prior to launch, everything that needs it is chowned to spot:spot permissions, EVEN the sym-linked .librewolf directory in /root......which at shutdown, is deleted again.

Suffice it to say, it all runs very sweetly indeed.

---

I'm NOT going to be building this on a regular basis. I won't NEED to. You, the user, can easily upgrade this yourself.

• Keep an eye on

  https://gitlab.com/librewolf-community/ ... -/releases

  This is the download location for the AppImages, which appears to be the sole package format these are released in. Download the current version, and extract it to obtain the AppImage itself.

• In the directory where the new AppImage is located, open a terminal (rt-clk->Windows->Terminal here). Run the following command:-

  Code: Select all

  ./xxxxxxxxx.AppImage --appimage-extract

  .....where xxxxxxxxx is the name of the AppImage exactly as it is written.

• This will unzip the AppImage, and leave a directory called "squashfs-root". This is basically a ROX-app; clicking on this will actually fire it up. However; what you want to do is to re-name this to the same as the one already inside the portable, so rename it to "LibreWolf64". Then, just swap this with the one in the portable.

• You have now upgraded LibreWolf to the new version, and can continue to use it with your existing profile.

Easy, isn't it?

---

The current portable can be found here:-

https://mega.nz/folder/bTJWCQSb#TXwTjaoWJwe_YRaDXkPB-w

Have fun!

Mike.

Hi Mike - firstly thanks for the new link. Got the download ok now.
I am somewhat confused though. The download is extracted as "LibreWolf-portable64" which looks like a normal roxapp or summat.
But when I click it and go inside - I then click the LAUNCH script and it doesn't run.
Manually running the LAUNCH script I get this:

Code: Select all

root# ./LAUNCH
fusermount: mount failed: Operation not permitted

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
open dir error: No such file or directory
root# 

...which sounds like what you were warning us about.

But it seems like your suggestions about extracting the appimage should not apply here - because my file is a "portable" not an "appimage" (i think..?)

So is the "portable" built in a way that should run? Or am I extracting it incorrectly? Or is the "LAUNCH" superfluous?

EDIT :" Oh - I just realised that if I click "LibreWolf64" instead of LAUNCH - it fires up.

My reason for testing this is the confusion experienced by Governor here: https://forum.puppylinux.com/viewtopic. ... 67#p133067

Anyway - hope you can understand something of my ruminations. Possible had one glass too many tonight

[fredx181]

Code: Select all

root# ./LAUNCH
fusermount: mount failed: Operation not permitted

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
....

root# 

...which sounds like what you were warning us about.

But it seems like your suggestions about extracting the appimage should not apply here - because my file is a "portable" not an "appimage" (i think..?)

...

When running the LAUNCH script it will run the appimage LibreWolf64 as spot. (clicking LibreWolf64 directly will run as root)
To fix the fusermount error (needed for to run as spot to set the "sticky bit" on it): chmod u+s `which fusermount` and it should work.

Btw, I've edited the LAUNCH script to this (profile in LibreWolf-portable64/LibreWolf64.home/ owned by spot, also downloaded files will appear in Downloads there (EDIT: If set to $HOME/Downloads in Librewolf settings, which is default btw) ):

Code: Select all

#!/bin/sh
#
# Launcher for 'portable' LibreWolf browser,
# edited by fredx181, librewolf profile folder in LibreWolf64.home/.librewolf
#
HERE="$(dirname "$(readlink -f "$0")")"

mkdir -p "$HERE"/LibreWolf64.home

chown -R spot:spot "$HERE"/LibreWolf64
chown -R spot:spot "$HERE"/apulse
chown -R spot:spot "$HERE"/LibreWolf64.home
#
LD_LIBRARY_PATH="$HERE/:$HERE/apulse${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
#
run-as-spot "$HERE/LibreWolf64" "$@" https://forum.puppylinux.com/index.php https://bleepingcomputer.com/forums/

2024-10-16_14-24-58.jpg (13.27 KiB) Viewed 796 times

[Governor]

When running the LAUNCH script it will run the appimage LibreWolf64 as spot. (clicking LibreWolf64 directly will run as root)
To fix the fusermount error (needed for to run as spot to set the "sticky bit" on it): chmod u+s `which fusermount` and it should work.

Btw, I've edited the LAUNCH script to this (profile in LibreWolf-portable64/LibreWolf64.home/ owned by spot, also downloaded files will appear in Downloads there (EDIT: If set to $HOME/Downloads in Librewolf settings, which is default btw) ):

Code: Select all

#!/bin/sh
#
# Launcher for 'portable' LibreWolf browser,
# edited by fredx181, librewolf profile folder in LibreWolf64.home/.librewolf
#
HERE="$(dirname "$(readlink -f "$0")")"

mkdir -p "$HERE"/LibreWolf64.home

chown -R spot:spot "$HERE"/LibreWolf64
chown -R spot:spot "$HERE"/apulse
chown -R spot:spot "$HERE"/LibreWolf64.home
#
LD_LIBRARY_PATH="$HERE/:$HERE/apulse${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
#
run-as-spot "$HERE/LibreWolf64" "$@" https://forum.puppylinux.com/index.php https://bleepingcomputer.com/forums/

2024-10-16_14-24-58.jpg

This script did not work for me, so what did I miss? When I click on LAUNCH, it opens in Geany
Thanks.

PS. bleepingcomputer is a malware site, IMHO.

[geo_c]

This script did not work for me, so what did I miss? When I click on LAUNCH, it opens in Geany
Thanks.

PS. bleepingcomputer is a malware site, IMHO.

Did you make the script executable?

[Governor]

This script did not work for me, so what did I miss? When I click on LAUNCH, it opens in Geany
Thanks.

PS. bleepingcomputer is a malware site, IMHO.

Did you make the script executable?

I just did it, thanks. The script did not work in bookworm, but it works in fossapup. I will try again later in bookworm.

[Governor]

This script did not work for me, so what did I miss? When I click on LAUNCH, it opens in Geany
Thanks.

PS. bleepingcomputer is a malware site, IMHO.

Did you make the script executable?

I just did it, thanks. The script did not work in bookworm, but it works in fossapup. I will try again later in bookworm.

Ok. LibreWolf will not start in bookworm, neither via the script nor the executable. I just downloaded a fresh copy from the @mikewalsh repository, and did the permission allow thing on the entire folder, but neither the script nor the executable works. Very frustrating.

[fredx181]

Ok. LibreWolf will not start in bookworm, neither via the script nor the executable. I just downloaded a fresh copy from the@mikewalsh repository, and did the permission allow thing on the entire folder, but neither the script nor the executable works. Very frustrating.

Yes, indeed not working in Bookworm, did some investigating and found that it has to do with the run-as-spot script included in Bookworm .
(don't know exactly what, other appimages also won't run as spot, btw).

Found that using the run-as-spot included in FossaPup works ok running from Bookworm.

Here's a .tar.gz containing scripts LAUNCH-as-spot , LAUNCH-as-root and run-as-spot (taken from Fossa) (these as a workaround for to run on Bookworm).
Extract in the LibreWolf-portable64 directory and run e.g. LAUNCH-as-spot .

Librewolf-portable-additions.tar.gz

Extract in the LibreWolf-portable64 directory

(1.27 KiB) Downloaded 22 times

but neither the script nor the executable works

Note that: once you ran the LAUNCH or LAUNCH-as-spot script, the folder LibreWolf64.home is owned by spot. Clicking the LibreWolf64 appimage directly won't work then because of that.
To fix that run chown -R root:root ./LibreWolf64.home from terminal standing in the LibreWolf-portable64 directory, to make LibreWolf64.home owned (again) by root.
(or run the LAUNCH-as-root script)

[Governor]

Ok. LibreWolf will not start in bookworm, neither via the script nor the executable. I just downloaded a fresh copy from the@mikewalsh repository, and did the permission allow thing on the entire folder, but neither the script nor the executable works. Very frustrating.

Yes, indeed not working in Bookworm, did some investigating and found that it has to do with the run-as-spot script included in Bookworm .
(don't know exactly what, other appimages also won't run as spot, btw).

Found that using the run-as-spot included in FossaPup works ok running from Bookworm.

Here's a .tar.gz containing scripts LAUNCH-as-spot , LAUNCH-as-root and run-as-spot (taken from Fossa) (these as a workaround for to run on Bookworm).
Extract in the LibreWolf-portable64 directory and run e.g. LAUNCH-as-spot .
Librewolf-portable-additions.tar.gz

but neither the script nor the executable works

Note that: once you ran the LAUNCH or LAUNCH-as-spot script, the folder LibreWolf64.home is owned by spot. Clicking the LibreWolf64 appimage directly won't work then because of that.
To fix that run chown -R root:root ./LibreWolf64.home from terminal standing in the LibreWolf-portable64 directory, to make LibreWolf64.home owned (again) by root.
(or run the LAUNCH-as-root script)

This is nice, I like having a choice. Although, I can't really see myself using spot, unless I know in advance a website could be risky, and I can't see myself having to maintain two different Librewolf profiles in two different folders. I don't suppose Is there is a way to use the same profile for spot and non-spot. The executable had stopped working, but is now working again; must be that extra command that fixed it:
chown -R root:root ./LibreWolf64.home

[Governor]

Now then, gang.

After much head-scratching, here is the new 'portable' version of 64-bit LibreWolf.

Initially, I thought this was going to be a "no-go". The last few LibreWolf AppImages that I've tried have, without fail, told me that they can't mount.....because Puppy's version of fusermount is WAY too old. From this, I take away the fact that these have probably been built by somebody who is running a 'bleeding-edge', rolling-release distro like Arch, which is constantly upgrading to the very newest of everything, all the time. Even Fossapup is nearly a year-and-a-half old now; in rolling-release terms, this is a lifetime!

But, there's 'workarounds' for pretty much everything, IF you put your considering cap on. Accordingly, I've run the AppImage with the

Code: Select all

--appimage-extract

....."-switch", which unzips it. And what you're effectively left with is a ROX-app. Which runs fine.

---

I've employed the techniques I've been refining with my recent rash of 'portable' applications. Instead of creating, and using, the profile directly within the portable itself, the profile directory is created inside the portable, and THEN it's sym-linked out to where the application expects to find it. At first run, the sym-linked directory is populated with all the profile stuff, though in reality it's actually writing direct to the portable anyway....

The sym-linked .librewolf profile directory sits in /root (the user's $HOME directory, in Puppy's case). However, LibreWolf still runs-as-spot. Immediately prior to launch, everything that needs it is chowned to spot:spot permissions, EVEN the sym-linked .librewolf directory in /root......which at shutdown, is deleted again.

Suffice it to say, it all runs very sweetly indeed.

---

I'm NOT going to be building this on a regular basis. I won't NEED to. You, the user, can easily upgrade this yourself.

• Keep an eye on

  https://gitlab.com/librewolf-community/ ... -/releases

  This is the download location for the AppImages, which appears to be the sole package format these are released in. Download the current version, and extract it to obtain the AppImage itself.

• In the directory where the new AppImage is located, open a terminal (rt-clk->Windows->Terminal here). Run the following command:-

  Code: Select all

  ./xxxxxxxxx.AppImage --appimage-extract

  .....where xxxxxxxxx is the name of the AppImage exactly as it is written.

• This will unzip the AppImage, and leave a directory called "squashfs-root". This is basically a ROX-app; clicking on this will actually fire it up. However; what you want to do is to re-name this to the same as the one already inside the portable, so rename it to "LibreWolf64". Then, just swap this with the one in the portable.

• You have now upgraded LibreWolf to the new version, and can continue to use it with your existing profile.

Easy, isn't it?

---

The current portable can be found here:-

https://mega.nz/folder/bTJWCQSb#TXwTjaoWJwe_YRaDXkPB-w

Have fun!

Mike.

No, it is not easy at all. Where is the download link, I can't find it on the page; which file is it?
Is there a difference between the file at gitlab and the file at the Mega repository?

I would think twice about sharing a link to bleepingcomputer.
I removed "https://bleepingcomputer.com/forums/" from the launch script because I have witnessed some very bad stuff going on there in their "help" forum, and I want nothing to do with that site. Some of the volunteer "helpers" advise desperate Windows users to turn off all antivirus and security programs. then run an app that extracts detailed information from the user's system, including IP and MAC addresses, and post it on-line in the forum. Then the user is instructed to download and run an app which fixes Windows errors (but it contains a rootkit), and say yes to any dialog boxes that appear. When the rootkit is installed, the user can then re-activate their security programs. It is so obvious that I can't understand how they can get away with it, but they do. And yes, I downloaded one of their recommended fix-it programs, tested it, and confirmed it was a rootkit. There is no way the people running that site can't know that this is going on. And if they are too clueless to know, it is not a site I would trust for anything.

[fredx181]

I don't suppose Is there is a way to use the same profile for spot and non-spot.

If you switch between LAUNCH-as-spot and LAUNCH-as-root , the profile LibreWolf64.home/.librewolf is used for both.

BTW, I forgot earlier, but it may be good to add this as last line at the bottom of LAUNCH-as-spot :
chown -R root:root "$HERE"/LibreWolf64.home # revert back to root ownership
Then after you ran LAUNCH-as-spot it brings back ownership to root. So directly running the LibreWolf64 appimage (= as root) will work (and profile directory the same too , in LibreWolf64.home)

EDIT:

Where is the download link, I can't find it on the page; which file is it?

Appimages are here: https://gitlab.com/librewolf-community/ ... -/releases
Say you downloaded v131.0.2-1 LibreWolf.x86_64.AppImage , rename it to LibreWolf64 (and make executable), then to update, replace in the LibreWolf-portable64 directory .

[geo_c]

I don't suppose Is there is a way to use the same profile for spot and non-spot.

If you switch between LAUNCH-as-spot and LAUNCH-as-root , the profile LibreWolf64.home/.librewolf is used for both.

BTW, I forgot earlier, but it may be good to add this as last line at the bottom of LAUNCH-as-spot :
chown -R root:root "$HERE"/LibreWolf64.home # revert back to root ownership
Then after you ran LAUNCH-as-spot it brings back ownership to root. So directly running the LibreWolf64 appimage (= as root) will work (and profile directory the same too , in LibreWolf64.home)

Funny, I just wrote a very long post detailing how I set up LibreWolf.AppImage manually to do this very thing from KLs that log in a spot, but I deleted it after I saw this post.

As an aside, the last several months I began to run my Firefox clones like LibreWolf with the uMatrix extension all the time, which pretty much breaks all websites first and lets me trickle in the elements I feel okay running. Seems to be a great security combination. LibreWolf with a few more about:config tweaks and uMatrix.

[Governor]

8<------

As an aside, the last several months I began to run my Firefox clones like LibreWolf with the uMatrix extension all the time, which pretty much breaks all websites first and lets me trickle in the elements I feel okay running. Seems to be a great security combination. LibreWolf with a few more about:config tweaks and uMatrix.

I installed the uMatrix extension in FF, but where are the settings? I don't see a little icon anywhere either.

[geo_c]

8<------

As an aside, the last several months I began to run my Firefox clones like LibreWolf with the uMatrix extension all the time, which pretty much breaks all websites first and lets me trickle in the elements I feel okay running. Seems to be a great security combination. LibreWolf with a few more about:config tweaks and uMatrix.

I installed the uMatrix extension in FF, but where are the settings? I don't see a little icon anywhere either.

Yeah, sometimes getting the extension icons to display in the menu bars in Firefox is quirky. I end up fiddling around with the settings and the customize toolbar screen until I get it. I'll have to play with it more to tell you any concrete steps.

[d-pupp]

On the far top right of firefox nav bar there is a icon that looks like a puzzle piece.
That should show you any installed extension. From there you should be able to tell it to show on the bar.

[Governor]

On the far top right of firefox nav bar there is a icon that looks like a puzzle piece.
That should show you any installed extension. From there you should be able to tell it to show on the bar.

@geo_c
Yes, that's the ticket. Thanks!

[mikewalsh]

@Governor :-

PS. bleepingcomputer is a malware site, IMHO.

Er....huh?? 'Scuse me?? Pardon my confusion here, but......what on earth are you running on about? From what dark recess of your mind did you drag that "pearl of wisdom" up from? And what does it have to do with this thread, anyway...?

I don't think so! I joined there way back in 2015, and have been on the staff since early 2020 as a moderator.

BleepingComputer was founded way back in 2003, as a site for assisting Windows users with any and all issues, including - naturally! - the all-too-prevalent virus/malware attacks (and latterly, ransomware attacks). They have a dedicated sub-forum for all this, manned by a team of members who have been trained in how to deal with this kind of stuff. Said members have been trained through BC's own online "college"......which is recognised as a top-tier organisation by the entire global infosec community, and has been for years.

Of course you're going to find malware there, and LOTS of discussion about such. That's the site's primary 'stock in trade', after all....

It would be appreciated if you didn't "slag off" what is almost an institution in the Windows world....apparently, just for the hell of it.

Mike.