This page has been nominated for deletion.
The given reason is: Discontinued and not available in portage anymore
If you disagree with its deletion, do not remove this notice; discuss your objections on the associated discussion page.
xombrero is a minimalistic web browser striving to be compact, secure, and fast.
The principal difference between xombrero and other full-featured browsers is that the sophisticated security features are designed in, rather than added through an add-on after-the-fact. With a strong accent on staying out of the way, it doesn't decide for you what search engine you want to use or what certificate authority you want to trust. Heavy vim users will also find its vim-like keybindings convenient, as it is easy to surf the web completely from keyboard.
emerge --ask www-client/xombrero
The configuration file is named ~/.xombrero.conf and located in the home directory by default. Starting xombrero with the command-line parameter
xombrero -f .xombrero.conf
xombrero -f .torbrowser.conf
To simplify configuration xombrero allows to choose between two high-level modes of browsing: browser_mode and gui_mode. Each mode represents a number of low-level settings.
browser_mode and gui_mode MUST be the first entries in the configuration file!
Most users should use browser_mode and shouldn't tweak low-level settings manually unless they know what they are doing. There are two modes:
whitelist. Each of this modes and the settings they enable are listed below:
The settings for 'browser_mode=normal' are as follows:
# allow_volatile_cookies = 0 # cookie_policy = allow # cookies_enabled = 1 # enable_cookie_whitelist = 0 # read_only_cookies = 0 # save_rejected_cookies = 0 # session_timeout = 3600 # enable_scripts = 1 # enable_js_whitelist = 0 # enable_localstorage = 1 # enable_plugins = 1 # enable_plugin_whitelist = 0 # allow_insecure_content = 1 # allow_insecure_scripts = 1 # do_not_track = 0
The settings for 'browser_mode = whitelist' are as follows:
# allow_volatile_cookies = 0 # cookie_policy = no3rdparty # cookies_enabled = 1 # enable_cookie_whitelist = 1 # read_only_cookies = 0 # save_rejected_cookies = 0 # session_timeout = 3600 # enable_scripts = 0 # enable_js_whitelist = 1 # enable_localstorage = 0 # enable_plugins = 0 # enable_plugin_whitelist = 1 # allow_insecure_content = 0 # allow_insecure_scripts = 0 # do_not_track = 1
Of course, these settings can be overridden later in the xombrero configuration file. See the xombrero man page for a more detailed explanation of each of them. Also, a good explanation on how to configure the settings is given in the file /usr/share/doc/xombrero-*/examples/xombrero.conf.bz2 if the examples USE flag was enabled. The :set command can be used in order to view the enabled settings.
The browser's appearance can be adjusted to your likes by setting two high-level gui modes: classic (the default) and minimal. In the classic mode the browser looks like the most modern web browsers. The minimal mode is similar to the vi interface. The following low-level GUI settings are set by the high-level "gui-mode".
The settings for 'gui_mode = classic' are as follows:
# fancy_bar = 1 # show_tabs = 1 # tab_style = normal # userstyle_global = 0 # show_url = 1 # show_statusbar = 0 # show_scrollbars = 1
The settings for 'gui_mode = minimal' are as follows:
# fancy_bar = 0 # show_tabs = 1 # tab_style = compact # show_url = 0 # show_statusbar = 1 # show_scrollbars = 0
For more information, please see /usr/share/doc/xombrero-*/examples/xombrero.conf.bz2.
In addition to the browser modes listed above, there is also a number of other parameters, which can be set in .xombrero.conf. Examples of them are:
Managing SSL Certificates
Validating SSL Certificates is possible in at least two ways. Each of them depends on how much trust one puts in the certificate authority.
CA Certificate Files
This approach uses CA certificate files, which are stored in the /etc/ssl/certs/ directory. As WebKit only supports a single PEM file, one can simply concatenate all separate files into a single one with the following command:
cd /etc/ssl/certs/ && for i in `ls`; do cat $i >> ~/.xombrero/cert.pem; done
.xombrero.conf and add there this line:
ssl_ca_file = /home/user/.xombrero/cert.pem
The URL bar of the visited site will be colored green when the certificate is trusted. It will be colored yellow when the certificate is untrusted. The blue color signifies that the certificate was saved earlier in the ~/.xombrero/certs directory.
It is recommended to periodically recreate the
Due to a number of accidents where CA certificates were compromised and used in a man-in-the-middle attack, and as attackers not always alert the users that a well-done compromise has taken place, it makes sense to opt for another model of certificate validation. The approach is based on the assumption that the attacker cannot successfully compromise all nodes in the network and cannot always send tampered SSL certificates through different encrypted network routes. The following steps need to be taken:
1. Access a site using a non-torified browser;
2. Save the site's SSL certificate into ~/.xombrero/certs with the
:cert save command;
3. Next time the site is accessed, the URL bar will be colored blue. It shows that the SSL certificate sent by the site doesn't differ from the one saved in the local store;
4. Access the same site using a torified browser. If the color is still blue, it means that the certificate is valid. Access the site again using different Tor circuits and exit nodes. In all cases, the URL bar color must still be blue (except when you've got a tampered SSL certificate sent by a rogue exit node);
5. If the color is yellow, or red at any step, it means that the certificate is tampered. If the site sends the same certificate through different Tor circuits, and this certificate is still different from the one gotten at the very first step, it could probably mean that the internet connection was modified at some point. The more exit nodes send you the same certificate, the higher this probability is.
None of the steps described above needs a certificate authority one must put all trust in.
The user can run custom scripts on webpages with the run_script command. Let's consider as example the following script for watching videos from youtube and other sites supported by youtube-dl. Let it be located in the home directory and called
youtube_watch.sh like so:
mplayer -vo x11 -fs `youtube-dl --skip-download -g $1`
Then, the script can be called with the
:run_script ~/youtube_watch.sh command. To simplify it, these lines can be added to
cmd_alias = yt,run_script ~/youtube_watch.sh
Changing Default CSS
The browser allows to toggle the page style between the default cascading style sheet and a low-contrast color scheme. The stylesheet can be changed for the opened web pages by pressing the s key to do it just for the current tab, or S to change it for all tabs. It is also possible to add the
userstyle_global settings to the browser configuration file and provide the custom stylesheet, changing the overall look and feel of opened web pages.