News for hackers. Stuff that matters.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by abcd_f on Thursday May 29, 2014 @07:20AM (#7815675)
That's LavaBit 2.

I've been a long time TC user and if there's the trait it has it's the quality and a high degree of polish. And now looking at the diff and the screenshot of that in-app "Not secure" message, the polish is just not there. It feels like it was something that was slapped together in a rush or by someone who's not an original developer. The SF page alone is a big red flag. If you compare its nearly hysterical tone and ridiculous BitLocker advice to the tone and content of the actual app, they don't add up at all.

This leaves us with a handful of discrepancies between the last good state of the project and what's out there now. So it's either someone else's hackjob or it is original and the discrepancies are intentional. Then, factor in the .exe sig match, and it pretty much leaves only the latter option - the original devs made an absurdly non-TC-like release. The question is "why?"

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by dendory on Thursday May 29, 2014 @02:10PM (#7817680)
The whole message on the site makes no sense and I think that's on purpose. What likely happened is the US gov found the TC authors, then used their weight to try and get them to back door the binaries. Authors didn't want to, but couldn't publicize the letters without going to jail, so they made up the most ridiculous story for why they were giving up on the project, the best possible outcome so that they wouldn't go to jail and wouldn't subject users to the required back door.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by at-fates-hands on Thursday May 29, 2014 @03:58PM (#7818271)
This my first thought when I read it and how it ended so abruptly. Conspiracy theories not withstanding, it's clear someone or some agency got to the developers and they just pulled the ejection seat for their own legal protection.

Can't say I blame them. I've had the feds show up where I lived once and I nearly shit a brick when I realized what was going on. You never want the weight the government beating down your back.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by jordigh on Thursday May 29, 2014 @02:49PM (#7817876)
This is the most plausible explanation I have seen so far.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by selmnoo on Thursday May 29, 2014 @09:01AM (#7815981)
This is a pretty confusing case, hard to make much of it, LavaBit 2 is of course a possibility. But while we're making these theories, I wanna sound my wild theory: Considering that: (1) TrueCrypt authors go to great to keep their identities hidden, and (2) it turns out TrueCrypt is not free/open software -- TrueCrypt is actually a project by some spooky 3-letter agency.

But anyway, thoughts on alternatives? CiskCryptor (http://en.wikipedia.org/wiki/DiskCryptor) sounds like a nice one, it's FLOSS. Thoughts on it?

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by x1798DE on Thursday May 29, 2014 @10:27AM (#7816346)
I really don't think we need to be running to TrueCrypt alternatives quite yet. If Phase II of the audit comes back showing TrueCrypt as insecure, then it's time to start worrying about that, but given that everyone was happy to keep using TrueCrypt up until 1 day ago even though it hasn't been updated in over 2 years, I don't think there's any big rush to switch to something else even if ongoing development stops.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by simonw on Thursday May 29, 2014 @12:56PM (#7817192)
"given that everyone was happy to keep using TrueCrypt up until 1 day ago"

The same was true for OpenSSL a few weeks ago.

One of the most plausible theories is that the TrueCrypt developers found a gaping security hole (ala OpenSSL) and realised that releasing a fix for it would reveal the bug and compromise every TrueCrypt partition in existence, so they chose to kill the project rather than risk the safety of all of that currently encrypted data.

If that scenario is true, there's a big rush to switch to something else before the bug is discovered by other researchers.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by x1798DE on Thursday May 29, 2014 @02:29PM (#7817777)
Their warning about it being insecure is clearly a joke, as their alternate suggestions (particularly for linux and Mac) are ones that no one should ever take seriously. TrueCrypt passed Phase I of the audit, and Phase II of the audit is coming down the pipe soon enough. Also keep in mind that TrueCrypt is one of the most widely-used cross-platform drive encryption tools and has been for some time. It seems far more likely to me that TrueCrypt is secure than that a more obscure competitor, no matter what the developers say in a weird, cryptic message that everyone assumed was their site being hacked.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by slinkyavenger on Friday May 30, 2014 @05:04PM (#7824075)
That would make sense, especially with all the truecrypted drives in evidence lockers and whatnot - in other words, things that can't be properly upgraded.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by jdbernard on Thursday May 29, 2014 @01:12PM (#7817287)
If that was the case, why not fix the bug and then tell everybody to upgrade to the new fixed version ASAP?
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by hack37 on Thursday May 29, 2014 @02:17PM (#7817725)
by fixing the bug you tell everybody what/where the bug is and if anybody has a copy of someone else encrypted disk (think external backup, amazon etc..) they can decrypt it.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by skolor on Thursday May 29, 2014 @02:20PM (#7817737)
That's effectively the same thing as releasing details of the bug. It would take time to take the patch and figure out the bug from it, but it would be fairly easily done for a determined attacker.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by e40 on Thursday May 29, 2014 @04:03PM (#7818291)
TrueCrypt authors go to great to keep their identities hidden

I donated at least two times to them via PayPal. How anonymous could they be if they got funds via PayPal? Not very, in this day and age. I would image it's trivial for the US government to find their true names based on this fact alone.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by pekk on Thursday May 29, 2014 @04:55PM (#7818545)
Since this thread is all about paranoia, how did you verify that anyone ultimately received the funds?
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by e40 on Thursday May 29, 2014 @05:32PM (#7818716)
Obviously, I could not. truecrypt.org had a donate button which redirected to a paypal page, and I donated. I'm assuming they wouldn't set up a donation method that merely gave the funds to paypal.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by intelliot on Sunday June 01, 2014 @11:02PM (#7831681)
What's their PayPal identity?
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by higherpurpose on Thursday May 29, 2014 @10:52AM (#7816490)
If TruCrypt got taken over, it should tell us something that they recommended Bitlocker (about Bitlocker).
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by CWuestefeld on Thursday May 29, 2014 @01:57PM (#7817598)
There's another possibility that I haven't seen mentioned yet.

It could be that the developer(s) want to get out anyway. The fact that they've been doing it for so long indicates that they've got some strong feelings about privacy.

Perhaps they're staging the whole thing as their way out, to make a political statement, pushing us further to do something about the government's stand on privacy.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by wahsd on Thursday May 29, 2014 @09:08AM (#7815999)
I just don't quite understand the panic about microsoft not supporting XP anymore. It's not like that was a surprise announcement or even that the deadline was just met. It was April 8th....and TrueCrypt just now shut down in panic? ...Because XP support stopped??? WTF is going on?

It's not even like support means anything, other than that they will no longer improve or fix it, i.e., there's still time to migrate away as XP degrades. It says nothing about whether XP is secure in and of itself.

This whole incident is about as weird as weird gets.

I saw a post that suggested it might be a canary, i.e., an event that must be interpreted as a certain action having taken place...a negative message....an absence of an indication that everything is ok. But that also seems odd since I am not quite sure that if TrueCrypt people were who we all want to believe they were, would suggest using bitLocker. bitLocker??? Alone that suggestion smells like rotten fish just by its association with MS and the US government.

You should put money on the fact that it really was someone associated with certain ever increasingly fascist governments of, likely the USA or Israel, that compromised TrueCrypt in a way that set off an "auto-destruct" sequence. It's probably a reaction to the Snowden compromise, with increased funding and efforts to regain domination that he exposed by becoming even more totalitarian through an "Operation Kristallnacht" sprint against civilian institutions.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by tripzilch on Thursday May 29, 2014 @11:17AM (#7816627)
Another theory is that some component of the development environment to compile TrueCrypt requires XP. Remember the guy that tried to compile the TC source to match the binary?

https://madiba.encs.concordia.ca/~x_decarn/truecrypt-binarie...

He needed to get some older version of Visual Studio and a very specific combination of service packs and updates in order to get to matching (nearly) the entire binary.

Could it be that the devs really wanted to keep developing in XP because some part of their dev chain required it, but with support being discontinued they of course couldn't run XP and consider that computer "secure" to develop on?

Obviously, if this theory has some grain of truth to it, it can only be part of the explanation for the TrueCrypt weirdness that's been going on today.

If I had to bet on it, I would say it's most likely they got Lavabitten. But then still, the XP remark seems like a very odd choice if it's intended to function as a canary of sorts.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by Lx1oG-AWb6h_ZG0 on Thursday May 29, 2014 @01:03PM (#7817244)
> Another theory is that some component of the development environment to compile TrueCrypt requires XP

This seems unlikely: the screenshots in your link clearly show the source could be built on Windows 7. The trouble Xavier mentions is with the updates to VS2008 SP1, not Windows service packs.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by Bootvis on Thursday May 29, 2014 @03:27PM (#7818101)
I don't think that the EOL of XP has much do with it because they could simple air gap their Windows XP installation to continue development in a secure fashion.

Unless, of course, something more shadowy is going on.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by blueskin_ on Thursday May 29, 2014 @11:02AM (#7816549)
>But that also seems odd since I am not quite sure that if TrueCrypt people were who we all want to believe they were, would suggest using bitLocker. bitLocker??? Alone that suggestion smells like rotten fish just by its association with MS and the US government.

That's the canary.

Not only is bitlocker backdoored, and most TrueCrypt users would know that, but they also say it is available on all windows versions, which is eminently not the case.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by outworlder on Thursday May 29, 2014 @12:30PM (#7817032)
Isn't a canary something that is 'removed', not 'added'? As in, the canary warns by being absent.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by Zancarius on Thursday May 29, 2014 @01:22PM (#7817358)
Not in this case [1], or rather, not always. And if you consider where the term arose (canaries in mines), it's really an issue of state more than it is absence. If the state of the canary changes it's cause for alarm.

In this situation, warrant canaries (or maybe an NSL canary as the case might be) is a subtle indication that everything is no longer in a known-good state and something has been compromised.

Although given some of the comments by danielweber, I'm increasingly less inclined to believe this was a canary. Developers throwing in the towel might be a more plausible situation, no matter how disappointing that may be.

[1] http://en.wikipedia.org/wiki/Warrant_canary

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by nisa on Thursday May 29, 2014 @10:28AM (#7816350)
Just another theory but consider that the TrueCrypt team was always anonymous and considering that their licence is somewhat prohibitive for a open-source project it's not totally bonkers to assume that some agency or big coorporation developed TrueCrypt in secret and made it public to gain widespread assurance that there are no bugs in the code.

Maybe they migrated away from XP and have assurance that Bitlocker is safe for them or switched to something entirely different and have no interest or funding for development it anymore...

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by codeulike on Thursday May 29, 2014 @09:13AM (#7816025)
* bitLocker??? Alone that suggestion smells like rotten fish *

The Bitlocker recommendation does seem strange. But when you look around the Windows ecosystem, there isn't much else that could be recommended. What would you recommend Windows people use, other than Bitlocker?

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by easytiger on Friday May 30, 2014 @04:53AM (#7820863)
I find it interesting that it is only Microsoft Windows users really affected by this. What does that tell you about it as an ecosystem/platform?
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by codeulike on Friday May 30, 2014 @05:28AM (#7820932)
It tells me all kinds of things that we've all known since the 90s.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by easytiger on Friday May 30, 2014 @10:42AM (#7822025)
Having tried windows 8 recently i find it appalling how little it has changed. Even aesthetically it is diabolically a failure. There is no consistency and nothing makes sense. The removal of progress bars from system update functions is UX stupidity and having to reboot after every minor change is just embarrassing.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by dublinben on Thursday May 29, 2014 @10:48AM (#7816466)
TrueCrypt 7.1a is still safe to use. So is GPG.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by phpnode on Thursday May 29, 2014 @11:00AM (#7816539)
how do you conclude that any TrueCrypt version is secure in light of this disclosure?
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by blueskin_ on Thursday May 29, 2014 @11:03AM (#7816554)
Because this happened to 7.2. Chances are, this is a warrant canary, and people will take the last known good 7.1 (i.e. the one that is being audited) and build their forks from there.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by danielweber on Thursday May 29, 2014 @11:20AM (#7816641)
1. 7.2 just disabled things. It didn't introduce a vulnerability.

2. Warrant canary makes no sense. There is nothing for a warrant to grab.

3. Forking is legally troublesome. Just because you can see the source doesn't mean you can distribute the source.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by blueskin_ on Thursday May 29, 2014 @11:24AM (#7816679)
>1. 7.2 just disabled things. It didn't introduce a vulnerability.

I had a look at the diff; I have neither the time nor crypto-specific skill to do an audit, but there are plenty of code changes that aren't warnings in there.

>2. Warrant canary makes no sense. There is nothing for a warrant to grab.

No, but they could have theoretically been asked to introduce a backdoor from a Lavabit-style order.

>3. Forking is legally troublesome. Just because you can see the source doesn't mean you can distribute the source.

Do you think that will stop people? Even if there is some legal issue, the Streisand Effect always overcomes it. So what if a TrueCrypt fork can't use Github because of that issue? Is the world suddenly lacking good hosting providers, perhaps in Switzerland or similar? Has everyone forgotten how to set up a public git repo themselves? Somehow, I think not. So what if many devs will probably have to contribute anonymously? With a product such as TrueCrypt, they probably should anyway.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by danielweber on Thursday May 29, 2014 @11:42AM (#7816787)
been asked to introduce a backdoor from a Lavabit-style order

This makes no sense. Lavabit was compelled to turn over evidence it told the government it had, which is straightforward law. There is nothing "Lavabit-style" about "distribute a back door or else." You would need explicit legislation to allow that. If the developer's cat was kidnapped to force him to put in a backdoor, there is nothing "Lavabit-style" about that.

You do hedge with the word "theoretically," but "theoretically" this could be a message from the aliens.

Do you think that will stop people?

It will stop the smart people, and you need smart people to work on it. Otherwise you would only be allowed to distribute it by illicit means, and you could never trust it. It would be as trustworthy as warez sites. Why even bother with that nonsense?

Much saner to just build something new, having learned from TrueCrypt's experiences. For example, something that starts from the command-line and then has a GUI in top, instead of the reverse.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by john_b on Thursday May 29, 2014 @12:32PM (#7817049)
> "There is nothing "Lavabit-style" about "distribute a back door or else." You would need explicit legislation to allow that."

http://en.wikipedia.org/wiki/Bullrun_(decryption_program)

No legislastion authorizes that program, among many others. I think what the parent was referring to as "Lavabit-style" was the "compromise your users or face legal action" move. Turning over customer data or introducing a backdoor are both means to the same end, as far as the NSA is concerned.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by danielweber on Thursday May 29, 2014 @01:02PM (#7817232)
Is there something at that Bullrun link that shows the USG uses legal methods (or even illegal methods) to force product makers to insert backdoors into their equipment against the product makers' will?[1]

The NSA inserting backdoors into the product without the cooperation or maybe even knowledge of the vendor -- while troubling for any number of reasons -- is vastly different. Especially when giving advice to developers about how to stay in bounds with the law. If the metagame becomes "the government can legally force you to insert backdoors into your product" any developer faced with this threat might believe it, when he should know it's bunk.

[1] RSA allegedly got paid $10 million to make a change the NSA wanted. RSA customers should demand an answer, but that's not forcing the RSA. People get paid to do things all the time.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by scythe on Thursday May 29, 2014 @04:45PM (#7818502)
Not there, but in the historical record for sure.

>Hushmail stated that the Java version is also vulnerable, in that they may be compelled to deliver a compromised java applet to a user.

>http://en.wikipedia.org/wiki/Hushmail#Compromises_to_email_p...

>Hushmail turned over cleartext copies of private email messages associated with several addresses at the request of law enforcement agencies under a Mutual Legal Assistance Treaty with the United States.; e.g. in the case of U.S. v. Tyler Stumbo.

>if a court order has been issued by the Supreme Court of British Columbia compelling us to reveal the content of your encrypted email, the "attacker" could be Hush Communications, the actual service provider.

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by danielweber on Friday May 30, 2014 @07:55AM (#7821253)
Wow, Huhsmail was pretty silly with their claims:

the company that provides Hushmail, states that it will not release any user data without a court order from the Supreme Court of British Columbia,

This is malarkey. Someone in the US could say "I'll fight all the way to the Supreme Court!!!" but you would be a fool to trust your business to their determination. Especially if they say it about a subpoena, which means they haven't even retained a lawyer to ask about this. (If your business plan depends on being able to wage a legal battle, you really shouldn't be scrambling through the yellow pages for a lawyer when you get your first subpoena.)

Back to the topic, I'll have to point out that this still isn't evidence of a company being required to backdoor a product. Hushmail, the same company that thinks it can fight a subpoena for third-party data all the way to the Supreme Court, said "well, we might be compelled to backdoor our product." This is just more repeating of the meme without evidence. It's unfortunate because some developer who remembers Hushmail might take their ill-informed legal opinion as reality.

Of course, Hushmail had access to cleartext copies of the messages. That's the killer. The government has the right to evidence about third parties in your possession. (Canada derives from British law tradition like the US. The government's right to all evidence is a concept that goes back centuries. If you can show that Canada broke from this tradition I would be most interested.)

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by mpyne on Thursday May 29, 2014 @12:54PM (#7817179)
> No legislastion authorizes that program, among many others.

No legislation forbids it either. If the NSA is legally able to search/seize a given piece of information why would you think they should not be allowed to forensically analyze it?

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by sliverstorm on Friday May 30, 2014 @01:49AM (#7820477)
It's not a panic about XP. The presented reasoning is:

- XP is the only widely used version of Windows with no built-in FDE

- XP is finally, truly, EOL

So TrueCrypt no longer needs to exist.

(I'm not arguing that- that is what the message is saying)