On 11 January 2016 at 15:37, Stefan Kanthak wrote:
> Which but does not mean/imply that everybody abandons TrueCrypt.
The project has been abruptly killed by the developers without any
clear explanation. There's something fishy and it cannot be trusted
anymore.
Spend your time and energy on forks
"Michel Arboi" wrote:
> On 11 January 2016 at 15:37, Stefan Kanthak wrote:
>> Which but does not mean/imply that everybody abandons TrueCrypt.
>
> The project has been abruptly killed by the developers without any
> clear explanation. There's something fishy and it cannot be trusted
> anymore.
"Sarah Allen" wrote:
> TrueCrypt ceased development back in 2014.
Which but does not mean/imply that everybody abandons TrueCrypt.
> Please refer to the below link to migrate to an alternative
> (BitLocker) from TrueCrypt.
> http://truecrypt.sourceforge.net/
STOP posting on top, but DON'T stop
TrueCrypt ceased development back in 2014.
Please refer to the below link to migrate to an alternative (BitLocker) from
TrueCrypt.
http://truecrypt.sourceforge.net/
From: Stefan Kanthak
Sent: Friday, 8 January 2016 9:32 PM
To: fulldisclosure@seclists.o
to
> fulldisclosure@seclists.org
> ...
>
Message: 10
Date: Fri, 8 Jan 2016 14:32:51 +0100
From: "Stefan Kanthak"
To:
Cc:
Subject: [FD] Executable installers are vulnerable^WEVIL (case 20):
TrueCrypt's installers allow arbitrary (remote) codeexecutio
Hi @ll,
the executable installers "TrueCrypt Setup 7.1a.exe" and
TrueCrypt-7.2.exe load and execute USP10.dll, RichEd20.dll,
NTMarta.dll and SRClient.dll from their "application directory".
For software downloaded with a web browser the application
directory is typically the user's "Downloads" di
