Difference between revisions of "Vivaldi Browser"

imported>Handy
(Created page with " Note: The Free Software Foundation recommends us to NOT use any Chromium or Chromium code based browsers due them phoning G**gle (often). The Vivaldi team say that they h...")
 
imported>Handy
Line 111: Line 111:
I'd prefer, instead of uMatrix, to use NoScript in combination with RequestPolicy, unfortunately they are not available for Vivaldi.
I'd prefer, instead of uMatrix, to use NoScript in combination with RequestPolicy, unfortunately they are not available for Vivaldi.


'''Self Destroying Cookies''' - This one seems to have arrived since last I was looking into Vivaldi & it is the closest thing I can get to the Firefox add-on '''Self-Destructing Cookies'''. It is great, & at last I'm satisfied re. having an add-on that deletes all cookies (not in its white list) as soon as all tabs connected to the same domain are closed. BRAVO! This add-on is very easy to use too.


I looked at various Cookie handling add-ons in the hope of finding one that could replace Self Destructing Cookies, but there really is currently none to fill SDC's shoes at this point in time. Here is what I looked at, you may like one of them, though I think that uMatrix in particular in the above list of add-ons covers Cookies well enough when combined with the appropriate settings in Vivaldi's preferences:
A way to handle the '''Flash Super-Cookies''' is:
 
'''Vanila Cookie Manager''' Has been rated as OK (by kdemeoz), but still not really as good as required. (I've not used it, at this stage.)
 
'''Click&Clean''' - Deletes typed URLs, Cache, Cookies, your Download and Browsing History...instantly, with just 1-click on Click&Clean button!
 
'''Cookies''' - A powerful and easy-to-use Cookie Editor.
 
'''EditThisCookie''' - EditThisCookie is a cookie manager. You can add, delete, edit, search, protect and block cookies!


The '''persistent flash cookies''' are placed in
The '''persistent flash cookies''' are placed in
Line 126: Line 119:
You can make an alias to regularly delete them:
You can make an alias to regularly delete them:


  alias removevivaldi='rm -R -f ~/.config/vivaldi/Default/Pepper?Data/Shockwave?Flash'
  alias rmvflash='rm -R -f ~/.config/vivaldi/Default/Pepper?Data/Shockwave?Flash'
 
You can of course make the alias name "rmvflash" to be whatever suits you.


===Using Firejail to sandbox Vivaldi===
===Using Firejail to sandbox Vivaldi===


Firejail is not a Vivaldi extension/add-on. It is an extremely valuable security feature that can be used with not only Vivaldi, so I have added it in here below the privacy/security add-on section.
Firejail is not a Vivaldi extension/add-on. What it is, is an extremely valuable security feature that can be used with not only Vivaldi. So I have added it in here below the privacy/security add-on section.
 
'''Firejail [https://firejail.wordpress.com]''' is a very interesting & easy to use piece of software that was initially developed to make Firefox more secure by isolating it (putting it in a sandbox) from the rest of your system. Firejail has developed beyond that & can be used simultaneously on many parts of your system. It is worth reading about on Firejail site (linked to above).
 
Until recently there was no functioning '''/etc/firejail/vivaldi.profile''' that came with the firejail install. Now there is. On my system at least when I run the following command '''firejail vivaldi-stable''' I get an error when using that unedited vivaldi.profile & Vivaldi does not run.
 
On the other hand, when I run '''firejail --noprofile vivaldi-stable''' Vivaldi runs perfectly well & is listed when I use the '''firejail --list''' command in the terminal. The '''--noprofile''' option apparently stops Firejail from using the '''default.profile'''. So I added the default.profile to the start of the /etc/firejail/vivaldi.profile commenting out any parts that already existed in the vivaldi.profile & Vivaldi runs fine now when I call it with the '''firejail --noprofile vivaldi-stable''' in the terminal (or as is more common, after booting my machine into Openbox I call Vivaldi with that command which I placed into the Openbox Menu).


For anyone interested following is my edited '''/etc/firejail/vivaldi.profile'''
'''Firejail [https://firejail.wordpress.com]''' is a very easy to use piece of software, initially developed to make Firefox more secure by isolating it (putting it in a sandbox) from the rest of your system. Firejail has developed beyond that & can be used simultaneously on many parts of your system. It is worth reading about on Firejail site (linked to above).


## 28-Feb-2017: handy added the Generic GUI application profile & edited out
Beyond that, I can say that Firejail & Vivaldi work seamlessly. You need to start Vivaldi-stable like so: '''firejail vivaldi-stable''' Which is easy in any DE/WM that allows you to enter your own menu commands (I use Openbox where it is simple). Or, you can make a ~/.bashrc alias to call Vivaldi from the command line.
## lines already existing in the Vivaldi browser profile below.  
################################
# Generic GUI application profile
################################
##include /etc/firejail/disable-common.inc
##include /etc/firejail/disable-programs.inc
include /etc/firejail/disable-passwdmgr.inc
#blacklist ${HOME}/.wine
caps.drop all
netfilter
nonewprivs
noroot
protocol unix,inet,inet6
seccomp
##################################
# Vivaldi browser profile
noblacklist ~/.config/vivaldi
noblacklist ~/.cache/vivaldi
include /etc/firejail/disable-common.inc
include /etc/firejail/disable-programs.inc
include /etc/firejail/disable-devel.inc
netfilter
whitelist ${DOWNLOADS}
mkdir ~/.config/vivaldi
whitelist ~/.config/vivaldi
mkdir ~/.cache/vivaldi
whitelist ~/.cache/vivaldi
include /etc/firejail/whitelist-common.inc
# lastpass, keepassx
whitelist ~/.keepassx
whitelist ~/.config/keepassx
whitelist ~/keepassx.kdbx
whitelist ~/.lastpass
whitelist ~/.config/lastpass


==Add-ons that enhance Vivaldi==
==Add-ons that enhance Vivaldi==
Anonymous user