<commit_before><commit_msg>Adding README<commit_after># Truecrypt 7.1a Homebrew Tap  [![Build Status](https://travis-ci.org/trinitronx/homebrew-truecrypt.png?branch=master)](https://travis-ci.org/trinitronx/homebrew-truecrypt)

This tap is designed specifically for installing the last available working & audited build of Truecrypt, version: 7.1a

## Installation

Then, run the following in your command-line:

    brew tap trinitronx/homebrew-truecrypt

## Usage

**Note**: For info run:

    brew info truecrypt

Once the tap is installed, you can install `truecrypt`!

    brew install truecrypt

## Testing

To test Truecrypt's internal encryption/decryption algorithms:

    /Applications/TrueCrypt.app/Contents/MacOS/TrueCrypt --text --test

To test volume creation:

    /Applications/TrueCrypt.app/Contents/MacOS/TrueCrypt --text --create  --encryption=AES --hash=SHA-512 --filesystem=FAT -k '' --password=<PASSWORD> --size=500000 --random-source=/dev/urandom --volume-type=normal /tmp/testvolume.tc

To test mounting the volume:

    /Applications/TrueCrypt.app/Contents/MacOS/TrueCrypt --text -k '' --password=<PASSWORD> --protect-hidden=no --mount /tmp/testvolume.tc /Volumes/testvolume
    [ -e /Volumes/testvolume/ ] && echo 'PASS' || echo 'FAIL'

To test dismounting the volume:

    /Applications/TrueCrypt.app/Contents/MacOS/TrueCrypt --text --dismount /tmp/testvolume.tc /Volumes/testvolume
    rm /tmp/testvolume.tc

## Is Truecrypt still safe to use?

### TLDR;

As long as you use a good password, and ensure good random seed data... **YES!**

### 3rd Party Audit

Since the original developer's strange disappearing act and unsubstantiated claim that it was unsafe, it has now gone through [an official 3rd party audit][1], and has come away with an overall clean bill of health.

Only a couple very minor flaws were found as reported on multiple news & blog sites:

 - [ArsTechnica][2]
 - [The Register][3]
 - [Cryptography Engineering Blog][4]
 - [Is TrueCrypt Audited Yet][5]
 - [GRC][6]

As mentioned the largest potential flaw found was an unlikely special case where the Windows Crypto API _may_ fail and TrueCrypt would not issue a security warning, but overall the other flaws found are minor and the consensus is that it's still safe to use.  Perhaps the best thing that happened to TrueCrypt is that the author abandoned it... for it gave reason for people to take notice & actually give it an audit.  We now have enough conclusive evidence to reasonably determine it is safe to use to provide sufficient protection for sensitive data.

[1]: https://opencryptoaudit.org/reports/iSec_Final_Open_Crypto_Audit_Project_TrueCrypt_Security_Assessment.pdf
[2]: http://arstechnica.com/security/2015/04/truecrypt-security-audit-is-good-news-so-why-all-the-glum-faces/
[3]: http://www.theregister.co.uk/2015/04/02/truecrypt_security_audit/
[4]: http://blog.cryptographyengineering.com/2015/04/truecrypt-report.html
[5]: http://istruecryptauditedyet.com/
[6]: https://www.grc.com/misc/truecrypt/truecrypt.htm

## Credits

Credit for the original base formula comes from https://github.com/caskroom/homebrew-unofficial/blob/master/Casks/truecrypt.rb 


{'fraction_non_alphanumeric': 0.10620863536085723, 'fraction_numerical': 0.01481248030255279, 'mean_word_length': 4.2724252491694354, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 5, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '584899', 'n_tokens_mistral': 1028, 'n_tokens_neox': 932, 'n_words': 315}