4 ms·
It says derived programs shouldn't be called "TrueCrypt" and shouldn't be ascribed to the original publishers, which honestly seem like pretty mild requirements
by Lagged2Death 12y ago
It says derived programs shouldn't be called "TrueCrypt" and shouldn't be ascribed to the original publishers, which honestly seem like pretty mild requirements.
https://github.com/warewolf/truecrypt/blob/33c0b8457051796faae1249950cb896dca027e49/Release/Setup%20Files/License.txt https://github.com/warewolf/truecrypt/blob/33c0b8457051796fa...
- xcrunner529 12y agoThe big issue was the clause that didn't protect those who forked from copyright infringement or being sued and the devs said that was intentional. Although, i doubt they'd really want to come out and make themselves public to pursue that.
- cornholio 12y agoSo they are right off on the wrong foot, with that domain name. I belive any TrueCrypt fork should require contributions to be dual licensed under TrueCrypt's original license and BSD. In time, the project can shed original files and re-implement them under BSD or any other GPL compatible license.
- Angostura 12y agoSo far there isn't any derived code. The truecrypt.ch domain seems a reasonable place for people to regroup. If/when a new release comes out, the community can think about a new name and register a new domain.
- jordigh 12y agoThe Truecrypt licenses also say that it cannot be sold, which makes it non-free and non open source. The OSI even said, "it is not at all appropriate for [TrueCrypt] to describe itself as 'open source.'" http://www.infoworld.com/d/open-source-software/truecrypt-or-false-would-be-open-source-project-must-clean-its-act-230862 http://www.infoworld.com/d/open-source-software/truecrypt-or...