Achieving Browser Privacy

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Lob

What could possibly go wrong?
Nov 7, 2020
161
44
With the recent news that DDG browser is "receptive" due to contractual terms to MS trackers (to an extent), I am wondering what the SN audience here are doing for their standard browser experience. Here's my basic setup:
  • Edge Chromium (because of native vertical tabs)
  • uBlock Origin
  • Cookie AutoDelete - with most cookies cleaned after 30 minutes bar a few sites I white/greylist
  • Don't F--k with Paste - because I like to paste in passwords generated with....
  • Bitwarden for password management
Am I missing something? PrivacyBadger, for example, would it add anything to my life?

Frankly, I know I will end up tracked somehow because it all comes back to my IP address. I don't care about that, it's the price I pay for using TCP.
 
This -- "Edge Chromium (because of native vertical tabs)"

What happened to native vertical tabs on Chrome? I thought it was supposed to be, oh, about 20 major revisions ago?

I'm stuck on a corporate laptop with using either;

Chrome with no vertical tabs, but I have over 80 open tabs AND my Lastpass extension, OR
Edge with vertical tabs, but NO extensions whitelisted (so far, and IT says they are too busy to deal with that right now).

I know, on a corporate laptop I have no privacy, but I want my LastPass, which the company whitelisted for Chrome a long time ago.

So, when is Chrome going to get native vertical tabs? I know I can search my open tabs on Chrome, but if the particular tab I'm using is 'off the right end' of the tab list, I can't manipulate it (drag it around, etc), except to close it with a Ctl-w.
 
Chrome with no vertical tabs, but I have over 80 open tabs AND my Lastpass extension, OR
Edge with vertical tabs, but NO extensions whitelisted (so far, and IT says they are too busy to deal with that right now).
Not gonna lie, I don't really know what that means. Whitelisted by whom? If it's his company then he should lobby his favourite IT professional.
 
Not gonna lie, I don't really know what that means. Whitelisted by whom? If it's his company then he should lobby his favourite IT professional.
This is a security forum, we should all be happy that our corporate Chromium browsers don't allow unvetted code to run on our corporate devices :D

I can actually say that I blocked the installation of any extensions on a Chrome deployment some years ago - firstly, above and secondly, nobody will pay the FTEs to vet the extensions that might be permitted. That at the time included LastPass because it was not leveraged in the corporate world and if you allow one password manager, you probably need to allow many.....it's not an easy situation.

anyway #blockunauthorisedcode
 
Well the issue with extensions is that the source is provided (they're written in JavaScript though, which is god awful write only code, IMHO.) The other issue is that they could theoretically be safe today and become unsafe tomorrow because the author could get hacked or could sell his dev/API key to another party. I don't know how the whitelisting works in a corporate environment, if each version of the extension needs to be whitelisted or if it's just the highlevel API key that is whitelisted and it's assumed the developer won't go rogue. The browser also has a permission model, and if you give an extension just the necessary permissions for tabs and not for all content, one would hope that would limit the risk of damage. Again, though, does the whitelisting expire if the permissions change?
 
don't forget the stories of extensions changing hands and then suddenly changing purpose.

and you're trusting the supply chain of what is usually some hobbyist.......