– You are using AxCrypt 2.
– You have shared the file key with the recipient, by adding the recipient’s email address to the list of users the file is shared with.
– You have sent the encrypted file to the recipient somehow, perhaps via email or by sharing via a cloud storage provider.
The recipient then needs to have AxCrypt 2 installed on his/her computer and has a verified AxCrypt ID account and has set his/her password.
The recipient then double-clicks on the file, signs in to AxCrypt if required, and the file opens.
Maybe it is a good idea to implement a function to encrypt files with AXCrypt but decrypt files with a password for users which not using axcrypt. In 7-Zip you are able to create .exe or .zip. Maybe it’s possible to do it that way too. Dear AX Team: what do you think?
As mentioned, yes we did remove that function because it promotes insecure user behavior, and also very seldom actually works. No major email provider will allow you to send .exe-files as attachments. A longer discussion is found here http://www.axcrypt.net/blog/avoid-self-decrypting-files/ .
However, if you for whatever reason cannot ask the recipient to download AxCrypt by including the link to the download page in the email with the encrypted attachment, why not just send the user two files? The encrypted attachment and the portable version of AxCrypt 2 (yes, it’s an executable, so it’s just as likely to fail as a “self-decrypting” archive).