Nothing is 100% fool proof. Hardware or software encryption both have their issues. Case in point, Truecrypt (on which VeraCrypt is based) had a few issues that ultimately led to its demise. Hardware devices (I saw mention of one SSD maker) a few or years ago would store keys on the device that could be read off. So you’re going to have to give me a source for “FDE is better done in software. It’s more secure” beyond “just trust me bro.”
How about you tell me why instead of just saying “TeRribLe AdViSe.”
The best option is going to be a USB drive that has an external key entry feature. Kingston IronKey has these and its as simple as enter a key and plug in. I use them at work and it works on all the major OSes. They’re not cheap though so if you want or are looking for a free solution then something like VeraCrypt portable and an encrypted container will be your next best option.
That was a fun read. Do recommend
It’s nice to see the work by the StarryExpanse people is finally going to see the light of day. It’s going to be a great nostalgia trip for me to play this one.
Also for those who don’t know, TheStarryExpanse was a project to rebuild Riven in 3D with a modern game engine. A few years ago they announced that they were going to collaborate with Cyan before turning over their work to them entirely and moving on.
At work we use the syslog log driver for docker. Essentially any container stdout gets pushed in to the system syslog that then gets ingested into splunk through one of their forwarders. We needed more than just container logs so that’s the reason for that. For a home setup I’d probably do the same but use the ELK stack instead of splunk.
I’m not sure what the original issues were either but I do remember the message on the TrueCrypt site that said something like “warning, do not use. Contains unfixed security issues.” The only thing that might explain that is this line from Wikipedia: “TrueCrypt includes two vulnerabilities in the driver that TrueCrypt installs on Windows systems allowing an attacker arbitrary code execution and privilege escalation via DLL hijacking” Personally I believe the guy just didn’t want to maintain the thing anymore and abandoned it with no notice. Either way. Good thing VeraCrypt took over and fixed all those issues.