Delete of unencrypted file from appdata/temp

[jim]

In axcrypt version 1, build 3180, it looks like after double clicking an encrypted file,  the encrypted file is opened, decrypted and written to the appdata/temp directory.  After the file is closed, the plain text file is deleted.  However, the file doesn’t appear to be wiped before deletion.  If I run a file recovery program the plain text file is available.  In axcrypt v2 does the process work the same way.   I’m concerned that the plain text file isn’t wiped even though using file recovery programs would normally need physical access to the computer hard drive.

[SvanteSpectator]

Hello,

AxCrypt 1 and 2 work the same way, as you describe, except that the original file *is* wiped. What you are seeing is probably temporary copies created by the application software itself, which AxCrypt has no control over.

This is why we always recommend to complement AxCrypt with full disk encryption for local device security.

There are other scenarios as well outside of AxCrypt’s control where the plain text may be made recoverable, such as shadow copies in Windows and journaling file systems.

If you can actually show an example where the plain text is directly recoverable after opening and closing a file with AxCrypt, please describe the exact sequence of events. Do be sure that there are no recoverable files *before* starting the test.

[Author]

Posts