Linked by Julian Djamil Fagir on Thu 14th Feb 2013 22:23 UTC
Thread beginning with comment 552739
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Truecrypt is open source, not closed at all.
by DaveK on Sun 17th Feb 2013 04:30
in reply to "RE: Truecrypt is open source, not closed at all."
"TrueCrypt is and always has been open source.
Just because the source is downloadable doesn't make it open source. It's quite possible that the truecrypt license is not compatible with Dragonfly BSD's goal and policies.
A cursory glance indicates that the license is such that it could not be included as part of any BSD. "
That's not what "closed source" means. If the article wanted to distinguish between free software and open source, it should have done so, but closed source is unquestionably the wrong one of the three terms to use.
RE[3]: Truecrypt is open source, not closed at all.
by metalf8801 on Sun 17th Feb 2013 23:17
in reply to "RE[2]: Truecrypt is open source, not closed at all."
While the license may have change since it was originally rejected it is still not recognized as ether an open source license by the OSI (Open Source Initiative) or as a free software license by the FSF.
http://en.wikipedia.org/wiki/Truecrypt
https://fedoraproject.org/wiki/Forbidden_items?rd=ForbiddenItems#Tru...
RE[3]: Truecrypt is open source, not closed at all.
by zima on Wed 20th Feb 2013 19:19
in reply to "RE[2]: Truecrypt is open source, not closed at all."
That's not what "closed source" means. If the article wanted to distinguish between free software and open source, it should have done so, but closed source is unquestionably the wrong one of the three terms to use.
Neither of the three terms is particularly good. "Shared source" would be probably the best description of Truecrypt.




Member since:
2005-08-18
Just because the source is downloadable doesn't make it open source. It's quite possible that the truecrypt license is not compatible with Dragonfly BSD's goal and policies.
A cursory glance indicates that the license is such that it could not be included as part of any BSD.