Why does it say I can “decrypt” a file that hasn't been encrypted yet?
Because you CAN. What it will do is effectively encrypt the file in reverse (so “encrypting” the resulting file will effectively decrypt it). This was an intentional design feature.
What happens if I use the wrong key to decrypt?
The program will run normally, but the output will be unreadable.
What happens if I use the wrong password when decrypting?
The program will run normally, but the output will be unreadable.
How strong is this encryption?
Cryptographic strength can be tricky to calculate. Because the program will always run, attempts at cracking (even if they also have the same program) would need to be manually checked to see the results, and they cannot ever be sure if they got an incorrect result or have successfully decrypted the file to find the contents were encrypted (layered encryption).
How many keys are there?
It would be an understatement to say that there are more possible keys than there are insects on the planet. The number is more than one hundred thousand digits long.
What happens if I lose my key file, can you recover it for me?
No, we do NOT keep a record of the keys we distribute. This is for YOUR security. In the unlikely event our systems are hacked, nobody can steal files that no longer exist. Your files are YOUR responsibility, including your keys.
Can I share my key(s)?
It's yours, do whatever you want with it. If you're intending to send encrypted files to other people, then they'll need a way to decrypt those files, right?
Why does it create a log?
For users who intend to use it for sending encrypted files who have Swiss-cheese memory. If you don't want it, delete it.
