[Cryptography] What is going on with TrueCrypt?

[Bill Cox]

On Sun, Jun 1, 2014 at 12:46 AM, Sidney Markowitz I intended to point out
that there might be problems forking the project under
>
> any license, with GPL being only the most obvious one with which there
> would
> be a problem.
>

I agree with your analysis so far.  TrueCrypt 7.1a looks forkable, but will
have to contain dead links, and can't have a name similar to TrueCrypt.  I
think it is OK to point out that the link is dead on the page containing
the link (probably the About page).  This license does look like no IP
lawyer ever looked it over, but I don't think it's a problem other than for
inclusion in Linux distros that are very careful about their licenses, such
as Debian.

We don't have the right to change the license, so we can't re-release this
code under any GPL license for example.  It will have to continue to be
released under the license that shipped with 7.1a, though more restrictions
can be added for new code if anyone wishes.

Perhaps the code can be replaced over time, and the new code licensed under
some other form, but I think that's low priority for the near term.  There
are already FOSS alternatives with decent FOSS licenses that would make a
better starting point if having a Debian compatible license is the goal.

Perhaps the new TrueCrypt maintainers could work with one of those FOSS
alternatives, and over time converge on a common properly FOSS licensed
crypto core.

Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.metzdowd.com/pipermail/cryptography/attachments/20140601/a4206175/attachment.html>