TrueCrypt Gets a New Life, New Name
storagedude writes: Amid ongoing security concerns, the popular open source encryption program TrueCrypt may have found new life under a new name. Under the terms of the TrueCrypt license — which was a homemade open source license written by the authors themselves rather than a standard one — a forking of the code is allowed if references to TrueCrypt are removed from the code and the resulting application is not called TrueCrypt. Thus, CipherShed will be released under a standard open source license, with long-term ambitions to become a completely new product.
Suddenly I think of banjos.
Here's hoping the audit is a success.
allow a fork to be released under a standard open source license?
Because I can take software with a standard open source license and put TrueCrypt's name back into it.
Not that I intend to do so, but it just seems off, somehow.
If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
Just curious. Is there some kind of unwritten rule that FOSS project names have to as crappy as possible? Is it just a translation thing, where maybe the name makes more sense or sounds better in the dev's native tongue? Has anyone been part of a FOSS project and was involved in the naming of it?
How long before they get a FISA or PRISM notice?
Wonder if they will have a "Warrant Canary" posting.
They're obviously using my HorribleNameGenerator library. I'm proud to have contributed to so many FOSS projects.
Nothing inspires more confidence in a complex cryptographic system than a name like "CipherShed.'
Is the geek born with this impulse to shoot himself in the foot?
They've already screwed the pooch.
They've published the source archive under the original TrueCrypt license. As a result, unless there's a legal entity (person or company) to which all contributors make an assignment of rights, or they keep the commit rights down to a "select group" that has agreed already to relicense the code, they will not be able to later release the code under an alternate license, since all contributions will be derivative works and subject to the TrueCrypt license (as the TrueCrypt license still in the source tree makes clear).
The way you do these things is: sanitize, relicense, THEN announce. Anyone who wants to contribute as a result of the announcement can't, without addressing the relicensing issue without having already picked a new license.
Lots of great things have been invented in a shed.
"When information is power, privacy is freedom" - Jah-Wren Ryel
Like TVR.
Veracrypt seems to be similar inconcept but has made several releases so far and added some fixes from the code audit. This one OTOH has yet to release a version. It'd be good to have someone emerge the "generally recognized best" successor.
Veracrypt is also a one-man copyright fraud. No, not just infringement but as in actually taking the Truecrypt code and slapping another license on it. That project stinks to high heaven.
Live today, because you never know what tomorrow brings
This news seriously made my day (an no I don't care about the name). I have TrueCrypt running on all my machines and couldn't live without it. It gives me great piece of mind should a computer be stolen or lost. TrueCrypt was a breathe to install and use and, while I have not looked into the code, is vastly superior to having no encryption at all or using a commercial product which is almost certainly back-doored. I hope this project gets off the ground.
Is really writing the code?
"If any question why we died, Tell them because our fathers lied."
They hope to rewrite and replace code until they have something new they can release under a standard OSI-approved license.
LAME was developed in the same way, by replacing pieces of the ISO's reference MP3 encoder until it was finished in May 2000. Is there a better name for this "ship of Theseus" method?
Crappy ones: GIMP, Tahoe-LAFS, Ubuntu, Kdenlive, XFCE...
As a user of Xubuntu who brings out the GIMP at least twice a week, I'm interested in how you'd name them better.
For the sake of keeping these tools out of the greedy hands of corporations, I'd almost be okay with using GPL for this project. It's not a cool license for developers, but I'd almost consider the value for end-users more important in this case. Locking this technology up behind a paywall won't do anyone any good.
CipherShed indeed.
I am very small, utmostly microscopic.
It's interesting though, if the authors of TrueCrypt really do want to stay anonymous... how will they ever exercise their copyright? Or for that matter prove that they ever owned the project in the first place?
I like the doxbox project - it works with linux crypto containers as well. Its a fork of freeotfe that was always better than truecrypt because its easier to use and has a license that encourages people to contribute.
Their site says "proudly powered by wordpress". Err, "security", "wordpress", isn't that mutually exclusive?
no, I don't have a sig
This is great news and honestly, its the best news I've had today.
Really? But by implication you'd be totally fine with closed source (as in Microsoft)? Just asking.
It's not as if their excellent communication skills or competitiveness with professional programs has anything to do with it. They even got a reference in a Tarantino movie which I am sure was to honor their excellent contact with the graphics design professionals.
I was promised a flying car. Where is my flying car?
But then he sold one.
I think CiperhShed is one of the slickest names I've seen...
Yes, there is some poorly named Open Source software but the majority is really on-par with proprietary shit.
CryptKeeper, owned by HBO?
How is it a violation of TrueCrypt's license when TrueCrypt's license specifically ALLOWS for this?
For the idiots who can't even read the story: TrueCrypt's license allows for taking all the code and reusing it, with only requirement being using a different name.
Well we only had one Beer story today, so I nominate BeerCrypt. Because we all love beer and crypto. It's a no brainer and the quicker you bring Cipher-Shed behind the wood shed the better. Let Mcafee have Endpoint and Microsoft have BitLocker. Nice catchy names to make the most hard assed CEO blush and gush. BeerCrypt. You know you want it.
Why worry about squatters, if ironcrypt.org is taken just use ironcrypt.foo. My favorite open-source transparent crypto product uses doxbox.eu; doxbox.org is something else - who cares?
That's easy to pronounce, and since part of the intent of the encryption software is to present a disk with no evidence of there being an encrypted file, the 'invisibility' part may make sense to the nontechies.
I was going to suggest Data-B-Gone but that's probably trademarked by QVC :-)
https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
Thanks for posting this. I am the maintainer of DoxBox. If you have any questions or want to flame me about the name, go ahead.
Moderated Usenet
OneCrypt. One = true zero = false.
How about TildeCrypt, a pun on until decrypt-ed, for those who have had to wait hours to decrypt hp notebook hard disks before installing a bios and utility partition update before re-encrypting.
VeriKrypt would be a translation into mixed Latin & Greek.
Another catchy one that is easy to remember that most people could identify with would be "FortKnox"... a very secure environment for your valuables... Then again, maybe it is taken or trademarked or something.
or perhaps CipherIndexedArray?
I can't think of one for FBI. :)
CipherSecureInformationSystem
and
CryptSecureEasyCipher