On Fri, 30 May 2014 15:00:39 -0500, Brandon Perry
wrote:
>2) Do you trust these users to understand the codebase thoroughly enough
>and understand cryptography enough to not introduce stupid crypto bugs?
>That is a huge caveat.
It is - but it¹s also the risk you run with any open source crypt
On 30/05/2014 21:00, Brandon Perry wrote:
> Two issues with this:
>
> 1) TrueCrypt wasn't free as in freedom, it was free as in beer. These forks
> break the license afaik.
Not seeing this to be honest. I have taken a look at the 3.0 licence
(applicable to 7.1a), and can't see any real reason to st
If you want legit versions of TrueCrypt, look at DrWhax's repo where you
can independently verify the builds with the official TrueCrypt PGP keys:
https://github.com/DrWhax/truecrypt-archive
I think, given the nature of crypto, you should wait to pair/contribute
with Open Crypto Audit Project (OCA
Two issues with this:
1) TrueCrypt wasn't free as in freedom, it was free as in beer. These forks
break the license afaik.
2) Do you trust these users to understand the codebase thoroughly enough
and understand cryptography enough to not introduce stupid crypto bugs?
That is a huge caveat.
Just
Hi again!
There are at least two forks on GitHub of what appear to
be complete, legit versions of TrueCrypt 7.1 -- there are others
scattered throughout the web.
* https://github.com/syglug/truecrypt
* https://github.com/FauxFaux/truecrypt
Cloning and building on OS X,
figu
