So, it’s too much to expect widely comparable behaviour I guess, but enjoy the choice of DE and tools. not deprecated gruft) section for legacy KDE for a good dozen years. Yet, current desktop entries specification still carry a “special” (i.e.
Veracrypt github code#
Still, gnome3 got more difficult to customize all the time (e.g. It can be in a README on GitHub, for a demo on CodeSandbox, in code examples on Stack Overflow, or simply to test things locally. Personally, I do like that for regular use, but it boils down to personal preference. Clearly the behaviour is to simplify it for the user, yes. That aside, gnome-shell does trigger the tracker3.miner when the volume appears, so some automatism does work. I’m sure one of the multitude of mount-helpers for crypt-devices can handle that, but you can also use dolphin within gnome and see the veracrypt volume appear on the left upon mount. like Pastebin, social media or even code repositories, like GitHub, when talking about monitoring of. USB), but mounting from within veracrypt does not register as one. This is a technical feature comparison of different disk encryption software.
Encryption of the system partition adds a bootloader to the system which loads VeraCrypt on system start. Gnome-shell does have a automatism-trigger for removable drives (e.g. VeraCrypt is a popular open source encryption tool that may be used to encrypt files, create encrypted containers, encrypt entire hard drives and partitions, and even the system partition.
Perhaps that behavior is intended - perhaps this behavior depends on where you mount the encrypted folders to? It’s just not visible as an “external” drive?
0 kommentar(er)
