Re:TrueCrypt suggesting migration to BitLocker?
by prg318 on Wednesday May 28, 2014 @04:05PM
(#7812489)
SourceForge recently forced their users to change their passwords [1] because of an attack on their infrastructure [2]. Pure speculation but I'm not sure if that had anything to do with this?
[1] http://sourceforge.net/blog/sourceforge-net-global-password-...
Re:TrueCrypt suggesting migration to BitLocker?
by A_Non_eMouse on Wednesday May 28, 2014 @07:42PM
(#7813735)
Those two SourceForge blog posts are from January 2011, a year before the release of TrueCrypt 7.1a. The recent forced change was due to infrastructure changes.
Re:TrueCrypt suggesting migration to BitLocker?
by derefr on Thursday May 29, 2014 @02:20AM
(#7815008)
> Anyone running truecrypt already has truecrypt, right?
I frequently reformat my boot volumes—but I've had a .tc file laying around on an external HD since forever, with my websites' X.509 private keys and such inside.
I'm probably going to do exactly as this announcement says: download the export-only binary, create a loop-mounted LUKS volume, and migrate everything over.
Re:TrueCrypt suggesting migration to BitLocker?
by slashdotaccount on Thursday May 29, 2014 @06:05AM
(#7815508)
Recent versions of cryptsetup support decrypting truecrypt volumes, just use cryptsetup for both.
Even if it's a legit announcement, I wouldn't run that 7.2 binary. Anyone running truecrypt already has truecrypt, right? I don't know why they'd release a new version at the same time as such a dire and panic-inducing announcement.