Slashdot Mirror


TrueCrypt Audit: No NSA Backdoors

Mark Wilson writes: A security audit of TrueCrypt has determined that the disk encryption software does not contain any backdoors that could be used by the NSA or other surveillance agencies. A report prepared by the NCC Group (PDF) for the Open Crypto Audit Project found that the encryption tool is not vulnerable to being compromised. However, the software was found to contain a few other security vulnerabilities, including one relating to the use of the Windows API to generate random numbers for master encryption key material. Despite this, TrueCrypt was given a relatively clean bill of health with none of the detected vulnerabilities considered severe enough to lead "to a complete bypass of confidentiality in common usage scenarios."

10 of 142 comments (clear)

  1. Re:Quis custodiet ipsos custodes? by OzPeter · · Score: 5, Funny

    We need to audit the auditors of the auditors as well.

    So it's auditors all the way down?

    --
    I am Slashdot. Are you Slashdot as well?
  2. Very gratifying to see by sasparillascott · · Score: 4, Informative

    This was very reassuring to see and I'm very glad the audit was finished finally. The 2nd to the last version (v7.1a) is the gold standard for multi-platform encryption where you can be reasonably sure the NSA/FBI doesn't have a back door (or access to the keys) like they would with Bitlocker etc..

  3. Re: That's what they WANT you to believe! by Anonymous Coward · · Score: 5, Informative

    Look everyone, a NSA shill.

  4. What if the backdoor is well hidden? by buck-yar · · Score: 4, Interesting

    The shellshock bug went on for a long time with many eyes on the code. How do we know the auditors weren't outmatched and just missed the backdoor?

    1. Re:What if the backdoor is well hidden? by squiggleslash · · Score: 4, Insightful

      Who knows? On the other hand, the many eyes argument with ShellShock is dubious: most people who would have recognized it didn't realize the implications as they weren't looking at it from a security standpoint, and few people actually likely touched or had reason to view that part of the code.

      This story, on the other hand, is about an actual security audit. In theory, it is more comprehensive, the researchers were looking for bugs, had a security background and agenda, and so would likely have picked up on ShellShock had it been Bash they were auditing rather than TrueCrypt.

      I'm not suggesting there's no chance they've missed anything, but I am saying the process is considerably more thorough and less likely to make a mistake. Bear in mind TrueCrypt has had "many eyes" for a decade or so too. And "many eyes" did, eventually, pick up on ShellShock, it just took longer than anyone would hope.

      --
      You are not alone. This is not normal. None of this is normal.
  5. Re:Tin foil hat time by Andy+Dodd · · Score: 5, Interesting

    The only case I know of where an algorithm was actually backdoored was one of the random number generation schemes... The algorithm in question happens to be (IIRC) quite fast.

    In other cases (DES I think??? I could be wrong.) the NSA recommended some oddball changes. No one could find a negative consequence of them so they went in - a decade or so later, it turns out that the original implementation of DES DID have a cryptographic flaw and the NSA recommendations fixed that.

    Keep in mind there are two parts of the NSA, ones which have in many ways highly conflicting goals:
    1) One part is tasked with compromising the information infrastructure of our enemies - these are the ones who keep on making the news these days
    2) Another part is tasked with protecting our critical information infrastructure, especially with protecting data sensitive to national security. These are the people who do Type I crypto certification, worked on creating SELinux, etc. These rarely make the news but in general, from our perspective these are the good guys. You can tell that AES-256 is NOT backdoored by the NSA since they allow it to be used to protect classified information (NSA Suite B - you can assume anything in Suite B is solid since the NSA is using it themselves.)

    --
    retrorocket.o not found, launch anyway?
  6. Re:Tin foil hat time by Lord+Crc · · Score: 4, Informative

    There's talk that they influenced the decision of some recommended constants for Elliptic Curve Cryptography.

    You'll want to use constants that ensures the cryptographic strength of the algorithm, so picking them are non-trivial and hence a recommended set was published. This is the same for most algorithms. AES has constants and they are part of what makes the algorithm AES and not some other variant.

    Anyway, here's what Bruce Schneier said about ECC:

    I no longer trust the constants. I believe the NSA has manipulated them through their relationships with industry.

    https://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html#c1675929

    And here's a nice background on ECC:
    https://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curve-cryptography/

  7. Re:That's what they WANT you to believe! by Anonymous Coward · · Score: 5, Funny

    It enlarges your penis, citizen.

    You should compile with that flag every time for best results. Tell your friends.

  8. Re:Quis custodiet ipsos custodes? by Opportunist · · Score: 4, Funny

    Yet look how different they turned out to be. One became and upstanding, honest person who has never ever done anything but serving his country, and the other one went into politics.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  9. Re:Quis custodiet ipsos custodes? by Bob+the+Super+Hamste · · Score: 4, Funny
    --
    Time to offend someone