phc-discussions - Re: [OT] GeekCrypt: a Secure Fork of TrueCrypt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 03 Jun 2014 18:15:18 +0200
From: Milan Broz <gmazyland@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [OT] GeekCrypt: a Secure Fork of TrueCrypt

On 06/03/2014 05:32 PM, Bill Cox wrote:
> I've just about lost all hope that the guys running truecrypt.ch
> <http://truecrypt.ch> are competent to run a TrueCrypt fork.  They
> seem much more interested in raising money than securing the code,
> and they suggested adding an auto-update feature in their vision
> document, in addition to using funds raised from users to encourage
> continual feature enhancements.  The talk is about getting users to
> pay "lunch" once a year rather than securing passwords.
> 
> Therefore, I'm sending out a call for big geeks to join me in what
> I'm calling for now GeekCrypt.  It will be a TrueCrypt fork run by
> crypto geeks, and secured by geeks:
> 
> http://geekcrypt.net

Hi Bill,

just for your information, there is another independent and GPL
implementation of TrueCrypt format, inside cryptsetup code (Zulucrypt
uses it for opening volume while using tc-play for creating the TC volume).

Cryptsetup supports even old TC containers (in CBC and LRW mode
and all possible combinations, except some limitation caused by
Linux kernel), tc-play can open only XTS containers (but it
can also create them).
The underlying dm-crypt is the same.

(The inability to create containers in cryptsetup is intentional, adding
support for it is quite easy but primary format is LUKS. I do not
want to split resources, so focusing to own native LUKS format).
For more info see https://code.google.com/p/cryptsetup/

And to not to be completely of topic, my plan for next generation
of LUKS is to use new KDF from PHC finalist, I have already some
favorite candidates :-)

And yes, the cryptsetup is just for Linux (for now).

Sorry for off-topic,
Milan

p.s.
TrueCrypt fork is nice but I am afraid of license problems,
including possible inheritance code from E4M project etc.