You write: “Nobody can then blame AxCrypt if they lose their data“.
The unfortunate fact is that this happens on a daily basis in various similar situations, most commonly forgotten passwords.
Therefore, we’ll be requiring a user to enter the password again when changing options. We’ll still be getting some angry users blaming AxCrypt when they encrypted C:\Windows…
Hi – just adding my chorus to those who want subfolder encryption included as a feature or option. William makes a good suggestion. I would go so far as to say that this feature may determine whether my organization buys Axcrypt after the trial period is over.
I’m confused. Actually If I encrypt a directory using the contextual command “Encrypt” then it recursively encrypts everything. If I add a directory to “Secured Folders” it only encrypt automatically 1st level files.
From what I’m reading in this thread and considering the set-and-forget concept behind Secured Folders feature I’d expect to be the contrary. I really need a clarification.
Development is finished, and there’s just some testing to be done before release, planned next week. Just so it doesn’t come as a surprise, this feature is a part of the Premium Plan.