Context: A linux noob. I got a new laptop earlier this year and uses it mainly for tinkering/playing with linux, get competent with it before dropping windows completely on my main desktop. There is a lot of stuff I want to move back and forth between those machines during this learning period.
My idea is to use an external SSD which when I'm done with windows, I can still use it to store work files or any sensitive stuff, so it will need encryption.
Saw a reddit thread saying I still need veracrypt, which I'm totally ok with on windows side but I prefer keeping everything simple on linux side (I only know it can be done without any extra package)
Extra question:
I can possibly store all works and sensitive data on encrypt external and leave root drive unencrypted. In that case, which file system should I use on which drive? Does it matter?
From what I recall veracrypt is basically the only option, but I've never bothered setting it up myself, i just use luks on everything these days, but you won't be able to use that with windows, though it might be possible using WSL, but I don't know
VeraCrypt is the only company I use when it comes to encrypting external drives. Depending on what distro you use, you'll just have to select the proper file format. Aside from that, maybe encrypt 90% of the drive so there's some space for a few things which you can access without mounting the drive. When you go through the setup in VeraCrypt, it directly asks if the drive will be used with one or different systems, so they got you covered there. You can also find many video walk throughs online to follow along with as well.
I'm still a bit confused with veracrypt... The docs make it sounds like vc use its own format.
Can the drive be prepared with LUKS and then decrypt in windows with veracrypt? If not, I might just use bitlocker until I drop windows.
If things are still the same from ~ June of 2022 then you have a choice between none, Linux Ext2, Linux Ext3, Linux Ext4, and NTFS.
Edit: VeraCrypt utilizes a unique encryption process. Its easy as you just move the mouse around like you went mad, but this produces a highly secure encryption key too. As long as your distro works with NTFS then it seems VeraCrypt can assist to help you encrypt. Otherwise, when Windows is a VM it only can do what Linux allows it to do lol
Just a note: you can open Bitlocker encrypted drives on Linux, some distros (e.g. Mint and Fedora) have support for it out of the box that works via GUI file manager, I think it uses Dislocker under the hood
Looking at your use case, I think Veracrypt is the best fit. It can encrypt removable media, it can do WDE of both removable media and on-board storage, and you can pick the file system inside of the encrypted container (for compatibility's sake). And it has a GUI front-end for every OS Veracrypt will run on.
If you’re only using the external disk for days you could use ntfs with bitlocker and mount that in Linux. When your rest to fully migrate you could then do something Linux only if you wanted.
Yup, if you want Windows compatibility, it's the best. This is what I did. I created the disk in windows, standard NTFS, bitlocker encrypted. It mounts in Linux automatically asking for a passphrase with a popup.
Similar here, my work archive is Windows bitlocker password enabled. There is a linux package on SUSe that supports read write of Ntfs nicely, and GNOME promtps for bitlocker password. Easy Peasy
Depending on your specific situation, it could be a solid option to just jump in to whatever distro covers your needs best and just run Windows in a VM. On a current Linux device which previously ran windows, throw this in the terminal:
sudo strings /sys/firmware/acpi/tables/MSDM
and it will source the old Windows product key. You can also just jot down the key by pulling it up in Windows too. But regardless of how it's handled, it makes the VM setup an easier process for sure!
How about an alternate route? If transferring information between computers is the goal, you could skip the external drive altogether and put syncthing on both machines. Then you could just share the appropriate directories between the two without the go-between.