3 ms·
KeePass + VeraCrypt container, never failed me. Before that I used TrueCrypt but it is no longer trustable.
by Globz 9y ago
KeePass + VeraCrypt container, never failed me. Before that I used TrueCrypt but it is no longer trustable.
- _qbxp 9y agoWhat's the VeraCrypt container for? Isn't the DB already encrypted?
- Globz 9y agoYes but because I sync KeePass over Dropbox I want to hide the true content of my data and + it adds another security layer to break before getting to my Password vault.
- mehrdadn 9y ago> Before that I used TrueCrypt but it is no longer trustable. Really? Why?
- Globz 9y agoWell unless you are talking about TrueCrypt "next" - https://truecrypt.ch/ https://truecrypt.ch/ then yeah I guess this one is safe but I was talking about the original version from - http://truecrypt.sourceforge.net/ http://truecrypt.sourceforge.net/ WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues This page exists only to help migrate existing data encrypted by TrueCrypt. The development of TrueCrypt was ended in 5/2014 after Microsoft terminated support of Windows XP. Windows 8/7/Vista and later offer integrated support for encrypted disks and virtual disk images. Such integrated support is also available on other platforms (click here for more information). You should migrate any data encrypted by TrueCrypt to encrypted disks or virtual disk images supported on your platform.
- mehrdadn 9y agoOh, I did mean the original version. I was just asking because as far as I know, nobody has found any serious flaw in it. The developers have only stated that it may contain unfixed security issues because they are no longer supporting it. Consider that if any security issue was fixed in any of TrueCrypt's forks, then people would be saying TC is known to be insecure, and as far as I know this is not the case. So if you expect there to be any vulnerabilities in TC, you should also expect the same to be true for VC or TC.next, etc.