Ive been experimenting with pass-qubes in SecBrowser. I don’t think it would be an worse for fingerprinting than the current method (passwords stored in SecBrowser) but would be less attack surface.
Could a pass-qubes -> pass-secbrowser tutorial be added to the SecBrowser for qubes Qubes? The only packages needed are;
The only issue I see is https://github.com/kulinacs/pass-qubes does not have signed git tags. Since the rep needs little to no maintenance it could be forked to a “trusted” repo and git tags added?
- You could request signed git tags [template: https://github.com/HelloZeroNet/ZeroNet/issues/738].
- Also possible of course to fork a repo, review every file, and then create a signed git tag.
Are there any specific colors that are thought as being related to secuirty. For example, purple is related to anonymity.
I’m trying to come up with a color scheme for the SecBrowser landing page.
A post was split to a new topic: SecBrowser Welcome Page
Add content to first post of this thread. This is to avoid confusion when users click on one of the SecBrowser Welcome page links.
SecBrowser ™ is the fruit born from Tor Browser without Tor research and development.
Yes, we can always edit original posts add thread titles for improved expression, more up to date related to latest developments.
lock_pref() , l
ockPref() might be a workaround for these two issues. I think thats’ what TBB devs use to keep users from changing prefs such as the security slider default. it will likely break Tor Browser but cant hurt to try.
Actually it was originally https://github.com/sleutho/QuickJS but its name was changed to https://addons.mozilla.org/en-US/firefox/addon/quick-js-switcher/
Yes but we yet have to post
document prefs / settings to set security slider level
(this exact posting of mine: TODO research and document - How to use Tor Browser for security not anonymity? How to use TBB using clearnet?)
These two interactions with upstream need to be next.
Why is it not enough to just set the desired slider level in a prefs file that you ship in the browser profile (anyway)?
I think using the prefs approach is the one you should pursue right now. Shipping an own profile with customizations won’t go away in the forseeable future.
If the above is true, maybe the security slider not honoring the custom profile pref is a bug? Or perhaps we are missing something (not setting the correct pref?).
Regardless thats’ the solution imo. Lets lead off by asking why the security slider is not honoring the pref that we set. No reason to say anything about Whonix or SecBrowser.
Yes. We need to ask for how to set the pref. We can say that we know
there will be no environment variable and have to go the profile route.
It could be in form of a bug report “setting this pref does not work as
expected” or as enhancement request “please document how to do…” or it
could be asked on the mailing list as a question. Dunno what’s best but
anything can work, I guess.
Not necessary. I got it!
I was using either to many user_prefs (
extensions.torbutton.security_custom) or they were in the wrong order when setting the security slider, which was breaking SecBrowser.
It looked sane but I should have added one at a time.
These prefs set the security slider to “Safest”
user_pref("extensions.torbutton.inserted_security_level", true); user_pref("extensions.torbutton.security_slider", 1);
It might set the slider to highest but does it also do the action that
slider would apply when it is manually being set to highest? I.e. would
it actually disable scripts globally when started in this configuration?
Guess not. AFAICT there is no way to sync the slider with a pref. Bug report.
I’ve messed around with this before, and yes it does. You can test by looking to see if some of these about:config settings are set https://2019.www.torproject.org/projects/torbrowser/design/#other-security
- High … and disables SVG images ( svg.in-content.enabled ).
Does not work.
I speculate that
usingthe security slider in an interactive (manual) way makes it do things. However,
startingwith security slider pref set to high does not make the security slider do things. The pref only tells the security slider how it should visually appear but it does not seem to (fully) call the function which does things.
I think svg.in-content.enabled isn’t used anymore. Setting the security slider to high manually doesn’t change that pref for me but it does change svg.disabled to true.
File location moved.
new file location: