You are not logged in.
In my BL system, I have placed an executable wrapper at ~/bin/x-www-browser to launch firefox with firejail automatically whenever x-www-browser is used:
firejail firefox "@"
For system-wide usage, place the script at /usr/local/bin/foxjail instead and add it to the Debian x-www-browser alternative:
sudo update-alternatives --install /usr/bin/x-www-browser x-www-browser /usr/local/bin/foxjail 250
Offline
Firejail will jail a number of software packages and as I looked through the list I noticed Skype. Why would anyone want to firejail skype? The only thing I can think of is if you had malicious code in Skype itself because it was from a bad source. Or, is it possible to get something bad just by talking on Skype in Linux?
...
Linux in the backwoods of the Rocky Mountains...
Offline
Or, is it possible to get something bad just by talking on Skype in Linux?
Here's what I believe: Any program in general, which takes input from a user, a network or a file, is exploitable. If someone actively wants to target you in particular, they can and will. If someone's just casting a wide net, you can help avoid being caught up in it by reducing (minimising but not eliminating) your "exploitability". Practise more deliberate and safe computer use (not installing from random sources for example), and safer browsing by utilising easy to use software like firejail.
Best wishes
Red
Knowledge Ferret
Offline
I would recommend running the Skype web client from a firejailed browser, preferably within a container running in a VM over a Xen hypervisor.
8o
Offline
I would recommend running the Skype web client from a firejailed browser, preferably within a container running in a VM over a Xen hypervisor.
8o
thanks for the laugh.
Red
Knowledge Ferret
Offline
Firejail will jail a number of software packages and as I looked through the list I noticed Skype. Why would anyone want to firejail skype? The only thing I can think of is if you had malicious code in Skype itself because it was from a bad source. Or, is it possible to get something bad just by talking on Skype in Linux?
people really have to let go of the old "computer virus" concept.
surely this is still an issue (though i think it is much more concentrated on financial gain these days), but the common, everyday threat is that applications routinely have access to the internet, can sift your filesystem for exploitable data without you even noticing (it takes just 1s) and transmit it back to whoever "owns" the app/service (and you know who that is for skype).
firjail, if i understand it correctly, addresses both issues (malicious code & data mining) by presenting the app with a "jailed" environment, i.e. they never see your actual filesystem.
if you would start storing sensitive data inside the jail, at least the second point (data mining) would evtl. become moot, btw.
Offline
A question: does the "jail" persist after closing down the browser or whatever?
To put it another way, is it possible to use 'firejail firefox http://siteA.com' and 'firejail firefox http://siteB.com' without any risk of siteB having access to data left by siteA?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
For what it's worth, here's a really long-running thread on
FireJail - Linux sandbox
Using the Openbox (3.5.2) session of Lubuntu 14.04 LTS but very interested in BL :)
Offline
is it possible to use 'firejail firefox http://siteA.com' and 'firejail firefox http://siteB.com' without any risk of siteB having access to data left by siteA?
Yes, both instances would "see" different filesystem trees — check this by trying to upload something from the individual browser's file managers.
Offline
Yes, both instances would "see" different filesystem trees
isn't this really the same as saying the data is destroyed after closing that instance of firejail?
and is that configurable (meaning, in some instances it might be desirable to "return to a previously used jail")?
just checking if i understand the mechanism correctly.
Offline
Ah, it seems you need to use the --private option:
--private
Mount new /root and /home/user directories in temporary filesystems.
All modifications are discarded when the sandbox is closed.Example:
$ firejail --private firefox
I suppose that implies the data is not discarded otherwise?
EDIT Here:
https://firejail.wordpress.com/document … e/#private
"You can also use an existing directory as home directory for your sandbox, allowing you to have a persistent sandbox home."
Last edited by johnraff (2017-01-06 06:41:37)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
There is Firetools, which is basically a starter for firejailed applications. E.g. I had Midori installed and on Firetools there is the Midori icon available, so I can start the firejailed browser that way. Same with e.g. Firefox, Filezilla, VLC, etc. However: Firejail works with mpv, but its icon does not show up in Firetools (nor e.g. for Kate).
Offline