TrueCrypt must not die
truecrypt.ch
TrueCrypt must not die
1–10 of 103 posts
Re: TrueCrypt must not die
#2The signatures and binaries are not served over HTTPS. It would be prudent to compare them to other sources.
Re: TrueCrypt must not die
#3The signatures and binaries are not served over HTTPS. It would be prudent to compare them to other sources.
Just for reference, SHA1s posted from an independent source yesterday: https://news.ycombinator.com/item?id=7816109
Re: TrueCrypt must not die
#4I don't believe the TrueCrypt license allows this kind of redistribution, does it?
Then again, with anonymous developers and unknown jurisdiction, it may be moot.
Re: TrueCrypt must not die
#5I don't believe the TrueCrypt license allows this kind of redistribution, does it? Then again, with anonymous developers and unknown jurisdiction, it may be moot.
From a practical view the original authors were anonymous, would they really shed that to sue somebody forking their code against the license? Probably not.
Re: TrueCrypt must not die
#6I don't believe the TrueCrypt license allows this kind of redistribution, does it? Then again, with anonymous developers and unknown jurisdiction, it may be moot.
Looking at the license simplifications part of TrueCrypt 7.2 [1], it may be allowed.
[1] https://github.com/warewolf/truecrypt/compare/master...7.2#d...
Re: TrueCrypt must not die
#7This looks like a bootstrap site that was thrown together in an hour by two guys with twitter accounts and $10 for a domain name. I really doubt they're going to be doing any dev work.
Re: TrueCrypt must not die
#8I don't believe the TrueCrypt license allows this kind of redistribution, does it? Then again, with anonymous developers and unknown jurisdiction, it may be moot.
Looking at the license simplifications part of TrueCrypt 7.2 [1], it may be allowed. [1] https://github.com/warewolf/truecrypt/compare/master...7.2#d...
Upon skimming, it looks like it still retains some clauses like: "The name of Your Product (or of Your modified version of This Product) must not contain the name TrueCrypt [...] nor any other names confusingly similar to the name TrueCrypt" and "All graphics contained in This Product (logos, icons, etc.) must be removed from Your Product (or from Your modified version of This Product) and from any associated materials."
...but that actually doesn't seem all that insurmountable. Hm...
Re: TrueCrypt must not die
#9I don't believe the TrueCrypt license allows this kind of redistribution, does it? Then again, with anonymous developers and unknown jurisdiction, it may be moot.
Looking at the license simplifications part of TrueCrypt 7.2 [1], it may be allowed. [1] https://github.com/warewolf/truecrypt/compare/master...7.2#d...
TrueCrypt 7.1a - the one with the actual functionality - wasn't released under this license. It was released under the earlier one. And I don't think it allows for this version or later ala GPL. I'm not sure of this, though.
Re: TrueCrypt must not die
#10Also, it appears someone finally got a hold of a Truecrypt dev. The project was just shut down from lack of interest. No drama about auditing or, crazy NSA conspiracies after all:
https://twitter.com/stevebarnhart/status/472203503478509568
Edit: That tweet was deleted for some reason, but the rest of the thread is still there: https://twitter.com/stevebarnhart/status/472192457145597952