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

NOTE: As of macOS Catalina (10.15), 32-bit apps are no longer supported. Therefore, Truecrypt has been obsoleted. Please migrate to VeraCrypt which supports 64-bit. VeraCrypt is based on TrueCrypt 7.1a and is currently maintained.

To install VeraCrypt, the Truecrypt replacement: brew cask install veracrypt

First, make sure you have installed homebrew-cask if you haven't yet:

brew install caskroom/cask/brew-cask

Then, run the following in your command-line:

brew tap trinitronx/homebrew-truecrypt

Note: For info run:

brew cask info truecrypt

Once the tap is installed, you can install truecrypt!

brew cask install truecrypt

If you find this project useful and appreciate my work, would you be willing to click one of the buttons below to Sponsor this project and help me continue?

• ❤️ Sponsor
• 
• 

Every little bit is appreciated! Thank you! 🙏

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=test123 --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=test123 --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

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

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, 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
• The Register
• Cryptography Engineering Blog
• Is TrueCrypt Audited Yet
• GRC

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.

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