[Cryptography] GeekCrypt: A Secure Fork of TrueCrypt

Niklas Lemcke - 林樂寬 compul at coletteral.net
Fri Jun 20 00:17:47 EDT 2014


On Thu, 19 Jun 2014 20:10:42 +0100
Wasabee <wasabee18 at gmail.com> wrote:

> if i am not mistaken, the idea is to built upon TrueCrypt.
> Apparently, the devs don't want that to happen [0] - or is this a fake?
> If not, what's your next move?
> 
> [0] http://pastebin.com/RS0f8gwn

When he said "I am sorry, but I think what you're asking for here is
impossible.", he was referring to the question whether the TrueCrypt
trademark could be used, and whether the license of the code could be
changed. However, the license does allow a fork (with a few conditions,
such as using another name and pointing to the truecrypt site) under the
same license.

The road we are going down now is to

 - short-term:
	release a rebranded version to get rid of the license issues
and get used to the code and building process. Then release a version
with the fixes the audit recommended.

 - long-term: 
	replace (whether gradually or in one big effort has not been
decided yet) the parts of the code that are problematic license-wise
(apparently not all are, since TC also borrowed some crypto code) and
release under another license (BSD, MIT or GPL, has not been decided
yet).


The project has a website: ciphershed.org. Most of this has been stated
on the projects wiki.


-- 
Niklas

At the time of writing, no warrants have ever been served to me, Niklas
Lemcke, nor am I under any personal legal compulsion concerning the
CipherShed project. I do not know of any searches or seizures of my
assets.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://www.metzdowd.com/pipermail/cryptography/attachments/20140620/c63910b9/attachment.sig>


More information about the cryptography mailing list