Hello I am relatively new to qubes and still getting used to configuring things around.
From time to time I need to use some specific clearnet sites for my work but at the same time I do not want to give them my real ip or fingerprinting.
I wonder if I can make a disposable chromium based browser that will have persistent bookmarks and extensions and route its traffic through whonix.
Only the extensions and bookmarks must persist but everything else should reset after each usage.
The reason I want to route it through whonix is that on top of it I will use a VPN extension in the browser in order to be accessing clearnet sites that block tor. This VPN extensions dont always work as expected so in case of any leak I would like to stay safe that my real ip or dns is not leaking therefore the whonix reasoning behind it.
I will also use a user agent spoofer for every session to simulate android or windows devices
Can anyone guide me through this process if it is possible ? How to create such disposable qube ?
But as @apparatus wrote, there are ways to achieve some of your objectives.
You should also check this thread, and search the whole forum for “split browser” for many other discussions on the topic.
If you want extensions pre-installed there will be some fingerprinting (because the mere fact that you have them installed is part of what sites see) but with some effort you can at least avoid having the same profile show up every time (which is unique to you once generated). You’ll look like you could be anyone with the same taste in extensions.
One thing you can do, if there is some extension you like but don’t use very often, is to create one VM where it is installed, and another one just like it except that it is NOT installed. Then run that latter one except when you need the extension in question. That reduces your uniqueness online except for when you need that extension.
I believe that you’re better off separating your bookmark store from internet-browsing qubes completely. First of all, it negates the fingerprinting issue discussed in this thread by others. Secondly, it is just more convenient: what if you want to access a bookmark stored in one of your qubes from another one? By building your infrastructure around opening bookmarks from dedicated bookmark store you will both streamline this process and make it pretty software-agnostic.
It also gives you more freedom and control: since you don’t need to store bookmarks in your browser, you can use any software (with as much complexity as you want) to organize and access them.