When comparing Tox vs Email an encrypted .EXE file (AxCrypt), the Slant community recommends Tox for most people. In the question“What are the best ways to transmit sensitive information over the Internet?” Tox is ranked 8th while Email an encrypted .EXE file (AxCrypt) is ranked 11th. The most important reason people chose Tox is:
The code is licensed under GPL (may change in the future) and is available on [GitHub](https://github.com/irungentoo/toxcore).
Ranked in these QuestionsQuestion Ranking
Pro Free and open source
The code is licensed under GPL (may change in the future) and is available on GitHub.
Pro Multiple front-ends for multiple platforms available
At the moment there is no official Tox client, but a selection of 32 and 64 clients for Windows, OS X, Linux and Android is available.
Pro Privacy focused
Tox uses military grade encryption and works completely peer-to-peer.
Pro No recipient software needed if emailed as .EXE.TXT
After selecting "Encrypt copy to .EXE," rename the file to ".EXE.TXT" in order to bypass email provider restrictions on sending .EXE files. Windows will then warn you that the file will become unusable but ignore it and continue to email the file. All the recipient needs to do upon arrival is rename the file back to .EXE and ignore the Windows warning message. Then simply open the self extracting file and type in the agreed upon password between the sender and recipient. This is a great advantage of AxCrypt because it does not force your recipient to download any software.
Pro Available at right click
AxCrypt is an extremely convenient encryption program because it is always available at a single right click.
Pro Password protected and optional key-file
AxCrypt encrypts each file with a passphrase and an optional key-file. Transferring a key-file (that AxCrypt can generate for you) on a separate medium and the password on another medium to your recipient is the most secure option. Although a strong password alone will do. The only caveat is that the password and key file must be transferred to your recipient and the most secure way to transfer it is physically.
Pro Once created, does not depend on other software
As long as you have the password or keyfile to your encrypted file then you can still access it. This is beneficial if the software ever becomes unsupported.
Pro Free and open source
AxCrypt is free and open source. This is beneficial because anyone can examine the source code and check for errors.
Con Early stages of development
Since Tox is relatively new, it has important features missing (like group video) and requires a proper code review before it can be deemed reliable and ready for everyday use.
The receiver has to be running Microsoft Windows (or a binary compatible system, like Wine).
Con Opening an .EXE file may worry some recipients
Some recipients will be cautious of opening an .EXE and may end up ignoring it. It is a good idea to inform them in advance that you will be sending an .EXE and it is safe. Another precaution is to sign the email so the recipient knows that is you.
Con Anti-virus will likely block it
Most anti-virus block or strongly warn again executable in emails. You'll likely have to rename the file and so will the end user.
Con Untrusted / not signed
Unless it's signed (i.e., you can somehow validate the signature of the attached EXE file via another method) the EXE may actually be compromized (e.g., man in the middle) and do anything on your machine as your run it.
Con AES-128 encryption
AES-128 encryption is still extremely secure but it is a lower and more outdated level of protection than what other encryption programs such as 7-Zip offer.