{"id":14957,"date":"2014-05-29T15:40:24","date_gmt":"2014-05-29T15:40:24","guid":{"rendered":"http:\/\/kasperskydaily.com\/b2b\/?p=1931"},"modified":"2019-11-15T07:18:46","modified_gmt":"2019-11-15T12:18:46","slug":"truecrypt-unexplained-disappearance","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/truecrypt-unexplained-disappearance\/14957\/","title":{"rendered":"TrueCrypt: an unexplained disappearance"},"content":{"rendered":"

Something very weird is going on with the popular free whole-disk encryption suite TrueCrypt<\/a>. The story is still developing, but it does look like the suite ceases to exist right now. The only explanation its creators have provided so far is that using TrueCrypt \u201cis not secure as it may contain unfixed security issues\u201d<\/a>.<\/p>\n

\n<\/p>

What kind of issues? \u2013 This is something people behind TrueCrypt have not disclosed so far. There are some speculations about the possibility of a backdoor in the software code, but it\u2019s guesswork at best. There was also speculation of a possible deface: TrueCrypt\u2019s official site started redirecting people to the suite\u2019s Sourceforge page all of sudden. Now, however, there is a sort of a consensus that it wasn\u2019t a deface: along with redirect, the software itself is altered too, and now it is showing the very same warning as the Sourceforge site does. Users of TrueCrypt are recommended to migrate from TrueCrypt to Microsoft\u2019s BitLocker: TrueCrypt\u2019s developers offer a step-by-step instructions on how to do this.<\/p>\n

TrueCrypt is (well, was) a cross-platform, freeware, \u201csource-available\u201d encryption application that could create a virtual encrypted disk within a file or encrypt a partition or (under Microsoft Windows except Windows 8 with GPT) the entire storage device (pre-boot authentication). It\u2019s been around for almost 10 years, and all this time its developers stayed away from the limelight, even keeping their names in secret.\u00a0<\/p>

TrueCrypt\u2019s developers suddenly abandoned the suite without explaining the reason.<\/p>Tweet<\/a><\/blockquote>\n

The suite was highly praised for its stability, a formidable feature set, support of parallelized encryption for multi-core systems, and, specifically, \u201cplausible deniability\u201d function which allowed a single \u201chidden volume\u201d to be created within another volume.<\/p>\n

The developers had acknowledged that TrueCrypt is vulnerable to a few known attacks, for instance it may fall victim to a \u201cStoned\u201d bootkit, so additional security measures should be applied. Other than that, TrueCrypt mostly received high acclaim, except for the vagueness of language in its license, which is unique, and differs from widely used open source and free software licenses since it contains distribution and copyright-liability restrictions.<\/p>\n

By May, 2014 the software had been downloaded 28 million times. And now developers seem to have pulled the plug abruptly, and it does look like a withdrawal \u2013 a retreat from the uneasy world of encryption, which is made much more uneasy than before by E. Snowden\u2019s revelations last year.<\/p>\n

Actually, it was those revelations that, in part, led to a demand for an independent security audit to find out whether the suite might be tampered with at a certain point. A John Hopkins University\u2019s cryptographer and research professor Matthew Green, a long-time \u201cskeptic\u201d of TrueCrypt launched a dual crowdfunding campaign to get such audit funded. The community has shown a strong interest: Green eventually managed to collect as much as $70,000 (way above the campaign\u2019s set goal), and the first round of audit had been successfully completed earlier this year, yielding no adverse discoveries. The second phase hadn\u2019t even started yet, and now it looks there may not be one. Due to the \u201cclouded\u201d legal status of the TrueCrypt source code it is unclear if anyone would be able to pick up the development.<\/p>\n

So, let\u2019s put it straight: For now, nobody except for the TrueCrypt\u2019s developers themselves, of course, actually know what is going on. No information on the nature of the security issue and the possibility to fix it.<\/p>\n

The software was popular: 28 million downloads is a large amount itself, and even if only one third of those who downloaded the suite have actually been using it, that\u2019s the population of a large city. Migration to BitLocker is actually available \u201cout of the box\u201d to some users, since it is only shipped with the top-tier versions of Windows (Vista, 7 and 8).<\/p>\n

All these people now question whether their data has been secure at all since the day they have started using TrueCrypt. A lack of explanation doesn\u2019t make them feel any easier.<\/p>\n

While it is a common wisdom that noone reads EULAs, users expect they can trust software vendors, no matter if the sofware is commercial proprietary or open-source and\/or free to use. The last thing people would expect from a software developer is a sudden vanishing into the mist without an explanation. This is not the way things should work. Especially in the information security area.<\/p>\n","protected":false},"excerpt":{"rendered":"

Something very weird is going on with the popular free whole-disk encryption suite TrueCrypt. The story is still developing, but it does look like the suite ceases to exist right<\/p>\n","protected":false},"author":209,"featured_media":15786,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[261,926,2097],"class_list":{"0":"post-14957","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-encryption","10":"tag-freeware","11":"tag-truecrypt"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/truecrypt-unexplained-disappearance\/14957\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/truecrypt-unexplained-disappearance\/14957\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/truecrypt-unexplained-disappearance\/14957\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/encryption\/","name":"encryption"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/14957","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/209"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=14957"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/14957\/revisions"}],"predecessor-version":[{"id":30914,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/14957\/revisions\/30914"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/15786"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=14957"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=14957"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=14957"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}