No edit summary |
|||
| Line 4: | Line 4: | ||
The main two issues are: | The main two issues are: | ||
Q: What is wrong with the license? | Q: What is wrong with the license? [[BR]] | ||
A: Short answer, lots. With every major revision of the TrueCrypt license, it becomes less risky, but it is still non-free. We are hopeful that a discussion between TrueCrypt and the FSF will help resolve the remaining issues, but this has yet to occur. | A: Short answer, lots. With every major revision of the TrueCrypt license, it becomes less risky, but it is still non-free. We are hopeful that a discussion between TrueCrypt and the FSF will help resolve the remaining issues, but this has yet to occur. | ||
Q: Maybe a pointer to the discussion or a summary of the discussion is in order | Q: Maybe a pointer to the discussion or a summary of the discussion is in order [[BR]] | ||
A: An older discussion is here: http://www.mail-archive.com/distributions@lists.freedesktop.org/msg00274.html | A: An older discussion is here: http://www.mail-archive.com/distributions@lists.freedesktop.org/msg00274.html | ||
Q: What alternatives could (easily) replace truecrypt? | Q: What alternatives could (easily) replace truecrypt? [[BR]] | ||
A: Sorry, this is not my area of expertise. | A: Sorry, this is not my area of expertise. | ||
Q: Would it be possible to spawn a new truecrypt and have a different license? | Q: Would it be possible to spawn a new truecrypt and have a different license? [[BR]] | ||
A: No. | A: No. | ||
Q: For instance could someone change it to being GPL-ed? | Q: For instance could someone change it to being GPL-ed? [[BR]] | ||
A: Only the TrueCrypt copyright holders could choose to do that, and they have never done so (afaik). | A: Only the TrueCrypt copyright holders could choose to do that, and they have never done so (afaik). | ||
Q: Or is that one of the problems? | Q: Or is that one of the problems? [[BR]] | ||
A: Strictly speaking, it is not one of the problems. The fact that the license is non-free is the primary problem. | A: Strictly speaking, it is not one of the problems. The fact that the license is non-free is the primary problem. | ||
Revision as of 14:17, 14 August 2009
Truecrypt license troubles
Currently I use truecrypt to encrypt private data. Reading the section on truecrypt spawns many questions. The main two issues are:
Q: What is wrong with the license? BR A: Short answer, lots. With every major revision of the TrueCrypt license, it becomes less risky, but it is still non-free. We are hopeful that a discussion between TrueCrypt and the FSF will help resolve the remaining issues, but this has yet to occur.
Q: Maybe a pointer to the discussion or a summary of the discussion is in order BR A: An older discussion is here: http://www.mail-archive.com/distributions@lists.freedesktop.org/msg00274.html
Q: What alternatives could (easily) replace truecrypt? BR A: Sorry, this is not my area of expertise.
Q: Would it be possible to spawn a new truecrypt and have a different license? BR A: No.
Q: For instance could someone change it to being GPL-ed? BR A: Only the TrueCrypt copyright holders could choose to do that, and they have never done so (afaik).
Q: Or is that one of the problems? BR A: Strictly speaking, it is not one of the problems. The fact that the license is non-free is the primary problem.