Forum Replies Created
-
AuthorPosts
-
Thank you, Wilberforce!
Hello Jobix,
I think you should update your version of AxCrypt.
August 30, 2017 at 12:57 in reply to: Not encrypting upon Sign Out from AxCrypt or when locking screen #7704Many thanks Ted!
Hello Gregory,
Yes, you’re right. The link I sent is about a slightly different concern, it’s about how to get a non-networked computer working with Premium. My bad.
As mentioned, in the future, we’ll implement a purchase system that would enable you to purchase a license without ever entering a password to our server, but right now we can’t do that since the payment is/must be tied to an account.
Still, as a work-around you could use the method mentioned in the link, and simply use a unique password not used anywhere else for the online part of the operation.
Hello Bill,
No, there’s no need (and not a good idea) to decrypt files before deleting. I’m just trying to understand what the problem is, and unfortunately right now it’s very unclear. Can you give more info?
Hello Bill,
I probably don’t see the full picture, but if you delete encrypted files while under the control of AxCrypt, you may indeed get unexpected errors if AxCrypt actually expects the files to be there.
Perhaps you can elaborate?
Concerning the offline license question, see https://forum.axcrypt.net/forums/topic/premium-on-windows-vista/ .
Hello KW,
It does not sound like it’s an actual AxCrypt problem, but we’ll try to help you out. Please contact our support, by emailing support att axcrypt dott net .
Include screen shots of the error messages and the AxCrypt window (if it’s there).
Hello Anonymous,
Sad to hear it – could you let us know just what it is you object to, causing you to “refuse to use AxCrypt 2.0“?
Hello Michael,
This is how mobile phones work unfortunately. Essentially, all applications are in their own sandboxes (lightweight virtual environments). They do not normally work directly in a shared filesystem, instead files are sent and copied between applications, so when AxCrypt opens a document in Total Commander for example – we send the file to it, and thereafter we lose control of what TC does with it. In this case, it keeps around in it’s local sandbox until you exit it.
You should always use device encryption on mobile devices to keep data there protected. AxCrypt is how you get it there safely, simply put.
Hello Tim,
There’s nothing special with CIFS or other network shares, but there are many many limitations with the type of user mode secure delete AxCrypt (and most similar utilities) use.
What we do, is simple overwrite the file with random data. If the file system “at the other end” for example is journalling and retains shadow or generational copies, this are still there. If the file system or underlying firmware, for some reason does not actually write the actual data of the original file (for example SSD disks), or detects that the file is deleted soon afterwards the caching mechanism could determine the writes are “unnecessary”.
AxCrypt secure wipe protects against standard recovery measures, but not necessarily against advanced forensic techniques. For that physical destruction is the only known method guaranteed to work.
Hello John & others,
Great to hear! Would it be possible for you to get those files from the trash and send them to support att axcrypt dott net ? They do not contain any sensitive information. At most, they contain the path and names to your list of recent encrypted files. I would like to see if I can reproduce the issue here to fix it for real.
Anybody else with the same problem – if you can send the text files in $HOME/.local/shared/AxCrypt to support att axcrypt dott net it would be great to aid us understand the issue.
August 24, 2017 at 20:26 in reply to: Password assigned to a file now a login password, ! don't have another! #7649Hello Don,
Happy it worked out for you. I should of course have included that third possibility: You mistyped, you misremembered – or someone else changed it. Sorry about that, but it was not entirely clear that the file was accessed / modified by multiple persons. I thought the other guy was just some other user of AxCrypt – not of the same file. My bad.
Hello John,
Would you please try the following:
Quit / Force Quit AxCrypt.
Use Finder and go to $HOME/.local/share/AxCrypt and delete all files there. Start AxCrypt. If it does not work, Quit / Force Quit it again, and go back to $HOME/.local/share/AxCrypt and send us the file ReportSnapshot.txt if it exists to support att axcrypt dott net.
Hello John,
Thanks for the input. That’s our main problem – all the machines we try it on it works. Our theory is that it’s a timing issue (also known as a race condition) that sometimes causes problems with the startup, which is asynchronous – i.e. several things are happening in the background at the same time we’re displaying the initial UI etc.
If you’re interested, please send a request for the release candidate mentioned above.
Please note – it’s not regression tested, it’s right off our build server.
-
AuthorPosts
