Page MenuHomePhabricator

Customized welcome page and bookmarks for I2P / Alt TBB (keyword: homepage)
Open, NormalPublic

Description

To avoid confusion of users we need a custom landing page for the second "special" TBB instance, that explains it won't connect to the clearnet for privacy reasons. The page would have the Whonix ASCII but none of the other clearnet links. Something along the line of "Attention: This browser is configured to connect to local proxies only. Please check bookmarks for possible destinations. Make sure you have installed/enabled the corresponding software."

Custom Bookmarks that point to:

  • I2P router config page
  • Any other major default eepsites
  • Freenet
  • Zeronet landing page

Other ideas welcome.

Details

Impact
Normal

Event Timeline

HulaHoop created this task.May 8 2018, 6:15 PM
HulaHoop triaged this task as Normal priority.
Patrick renamed this task from Customized landing page and bookmarks I2P/Alt TBB to Customized welcome page and bookmarks for I2P / Alt TBB (keyword: homepage).May 8 2018, 9:22 PM
Patrick updated the task description. (Show Details)
Patrick added projects: whonix-welcome-page, html.
iry added a subscriber: iry.May 26 2018, 10:53 AM

I realized the homepage was set by an environment variable.

/usr/lib/whonix-welcome-page/env_var.sh :

TOR_DEFAULT_HOMEPAGE="/usr/share/homepage/whonix-welcome-page/whonix.html"
export TOR_DEFAULT_HOMEPAGE

I am not sure how we can set different TBB instances to use different homepages. Any thoughts on this? :)

The starter script of the alternative TBB instance could overwrite this
global, default environment variable.

(Same syntax as quoted.)

Sounds ok?

Package tb-starter /usr/bin/torbrowser should be enhanced for the
alternative TBB instance starter (new command line switch?)?

iry added a comment.May 27 2018, 4:50 AM

The starter script of the alternative TBB instance could overwrite this

global, default environment variable.

I was thinking about this solution, the problem is that there maybe some confusion when two TBB instances running at the same time.

Let's say a user starts the Alt TBB, which sets the environment variable, then the user starts the normal TBB, which overwrites the environment variable again. Then when a new homepage tab is opened in Alt TBB, it actually shows the homepage of the normal TBB.

We may somehow detect if a TBB instance has been running and reject starting another TBB instance?

I don't know about running multiple Tor Browser's in parallel, but as
far as this environment variable is concerned, there won't be an issue
most likely.

iry (iry):

iry added a comment.

The starter script of the alternative TBB instance could overwrite this

global, default environment variable.

I was thinking about this solution, the problem is that there maybe some
confusion when two TBB instances running at the same time.

Let's say a user starts the Alt TBB, which sets the environment variable,

Set the environment variable only for the child process - not globally.

One cannot change environment variables globally without logout/login
(usually reboot) to my knowledge.

Like to test? Set sometest=1 in /etc/environment. Then `echo
"$sometest" in one konsole tab. Then export sometest=2`. Then `echo
"$sometest". Then Then echo "$sometest"` in another konsole tab. In
the other konsole tab it will still be set to the original value of 1.

then
the user starts the normal TBB, which overwrites the environment variable again.
Then when a new homepage tab is opened in Alt TBB, it actually shows the
homepage of the normal TBB.

I am sure we won't have this issue.

We may somehow detect if a TBB instance has been running and reject starting
another TBB instance?

This may or may not be required for other reasons but unrelated to
environment variables most likely.

I suggest a new forum thread for this.

Please reference

https://www.whonix.org/wiki/Advanced_Security_Guide#Multiple_Tor_Browser_Instances

since it might require improvements. It doesn't cover running them at
the very same time yet.