Axcrypt leaves many files visible (UNencrypted) even when program exited

[Juste]

Hello Friends.

I do not understand why so many talks on an extraordinary FAILURE of the product. Whatever situation, there SHOULD NOT BE unencrypted version of files hidden somewhere.

1. The Appdata folder should be externalised, in order to put it on a custom location

2. The working directory SHOULD BE ALWAYS EMPTY

Axcrypt can use programming technique to do this in memory, and protect it.

Amazing !

[Juste77]

<p>I do not understand why so many words on an extraordinary FAILURE of this software. Whatever situation, there SHOULD NOT BE unencrypted version of files hidden somewhere.</p><p>1. The appdata folder SHOULD be externalized in order to put it on a custom location</p><p>2. the working directory should always be EMPTY</p><p>3. Axcrypt must use memory to store its internal files, with protection</p><p>Amazing !</p>

[AxCrypt SupportModerator]

If AxCrypt or your system was shut down forcibly or unexpectedly, the application may not have had sufficient time to complete all pending operations. In such cases, upon restarting AxCrypt, you may be prompted to clean up and re-encrypt the saved files. Once the cleanup process is completed, the temporary files will be automatically removed and all recent updates restored.

[AxCrypt SupportModerator]

If AxCrypt or your system was shut down forcibly or unexpectedly, the application may not have had sufficient time to complete all pending operations. In such cases, upon restarting AxCrypt, you may be prompted to clean up and re-encrypt the saved files. Once the cleanup process is completed, the temporary files will be automatically removed and all recent updates restored.

In order to remove local temporary content:

1. Open the AxCrypt application.
2. Sign-in
3. Navigate to File > Options > Clear All Settings & Restart from the menu

The new AxCrypt application currently in Beta phase allows you to configure the temporary file path directory. Download here, install and sign-in. Follow the steps: Settings > Advanced Settings > App Configuration to set up personalized temporary folder.

[AxCrypt SupportModerator]

Arish Sharma, Nulls Brawl

If AxCrypt or your system was shut down forcibly or unexpectedly, the application may not have had sufficient time to complete all pending operations such as a cleanup which automatically encrypts the opened files. In such cases, upon restarting AxCrypt, you may be prompted to clean up and re-encrypt the saved files. Once the cleanup process is completed, the temporary files will be automatically removed.

In order to remove local temporary content:

1. Open the AxCrypt application.
2. Sign-in
3. Navigate to File > Options > Clear All Settings & Restart from the menu

The new AxCrypt application currently in Beta phase allows you to configure the temporary file path directory. Download here, install and sign-in. Follow the steps: Settings > Advanced Settings > App Configuration to set up personalized temporary folder.

[Juste77]

I do not understand why so many words on an extraordinary FAILURE of this software. Whatever situation, there SHOULD NOT BE unencrypted version of files hidden somewhere.

1. The appdata folder SHOULD be externalized in order to put it on a custom location

2. the working directory should always be EMPTY

3. Axcrypt must use memory to store its internal files, with protection

Amazing !

[Wayne Johnston]

I recently discovered this behavior, and I think I now understand why I’ve lost changes in an encrypted text file I have edited periodically over a few years.

Notepad++ (and also recently, good old Notepad) open up a file in a new tab.  If you make changes and save the file and kill off the tab – the text editor stays running if there are other tabs open.  So Axcrypt doesn’t re-encrypt/wipe the file in this temp folder.  You have to completely exit the text editor program for that to happen.

How did I lose changes?  I’m not completely sure.  But before discovering what I wrote in the above paragraph, I noticed these temp folders and deleted them.  Then the next time I opened up my encrypted file – it was as it was originally from years ago.  Although I had also been getting a popup about some exception because the password being empty – which of course it wasn’t.  The full scenario was I would double click on the .axx file, I’d type in the password if I wasn’t signed in yet, the text editor would come up on the decrypted file, then I’d get a popup about the empty password.  Somehow for years I guess I was editing the temp file, and it was never getting re-encrypted.

[Author]

Posts