Special handling for Veracrypt containers
Special handling for Veracrypt containers
At the moment, i have excluded my virtual drives that appear, when i mount Veracrypt containers, in order to prevent leakage from the file history and index files. Would it be possible, to index data for special drives like those containers in an encrypted way? Or to abandon that session data after usage, but still being able to use Everything while those drives are mounted?
Re: Special handling for Veracrypt containers
Please consider running a new Everything instance:
Launch Everything.exe with -instance "Private" and -no-db
For example:
Everything.exe -instance "Private" -no-db
"Private" can be any text you like.
This will launch a new named instance of Everything, along side your normal unnamed instance.
"Private" is shown in the window title and tray icon tooltip.
Setup this new Everything instance to index only your encrypted drives.
-no-db will disable saving and loading to your Everything.db on disk.
A fresh index will be built in memory.
An alternative to -no-db is to store your database on an encrypted drive (Tools -> Options -> Index -> Database location)
Also consider disabling Search History under Tools -> Options -> History.
Launch Everything.exe with -instance "Private" and -no-db
For example:
Everything.exe -instance "Private" -no-db
"Private" can be any text you like.
This will launch a new named instance of Everything, along side your normal unnamed instance.
"Private" is shown in the window title and tray icon tooltip.
Setup this new Everything instance to index only your encrypted drives.
-no-db will disable saving and loading to your Everything.db on disk.
A fresh index will be built in memory.
An alternative to -no-db is to store your database on an encrypted drive (Tools -> Options -> Index -> Database location)
Also consider disabling Search History under Tools -> Options -> History.
Re: Special handling for Veracrypt containers
I will try that, sounds promising. Thanks a lot!