Forum Replies Created
-
AuthorPosts
-
Hello Bob,
AxCrypt is a user mode client desktop application, and as such should work perfectly fine via remote desktop etc. It does nothing strange or advanced as far as the internal use of Widows API etc is concerned, so it’s very compatible.
From a compatibility point of view Premium is essentially identical to Business, so you can use the Premium trial month to evaluate fully in your specific environment. Contact support if you need to extend the trial period, we’re usually quite flexible with that (or just register a new account under a new email).
Hello Peter,
I’ve written a longer text on the fallacy of a multiple passwords strategy, you’re welcome to read it here: https://forum.axcrypt.net/blog/use-of-different-passwords/ .
It’s questionable if the Office password protection adds anything also, the problem being that Microsoft failed several times to implement it correctly, and now it’s often very hard to know just what version of the implementations is used in a specific situation. The most recent implementation appears to be “good”, but it’s often not used due to default settings for backwards compatibility etc. It’s complicated…
The idea with AxCrypt 2 is that you should use one single sufficiently strong password for all your needs. Also, we do provide a password manager, but I can of course understand concerns about that. However, stating “I’ve never been hacked, but LastPass has” is not really a valid argument. The most likely case is that on-one has tried hacking you, while thousands have tried hacking LastPass. The problem is that there is a big risk that the first one who tries to hack you succeeds, and you won’t know until it’s too late. In some ways, it’s actually a good idea to use a product or service which *has* been hacked, as long as the provider has acted correctly, and improved the product since. Then at least you know that someone has tried, found a problem, which subsequently has been fixed. That’s one known problem gone.
Hi Gene,
Literally anything? Even the menu or sign out?
Hi Gene,
Yes, that is the latest beta version. At what stage does it hang? What version of Android are you running in your device?
Hello Gene,
We have just released a new beta for the upcoming release. If you are not already a beta tester, sign up here: https://play.google.com/apps/testing/net.axcrypt.axcrypt2x . That will give you access to beta versions through the Play store.
Hello Ricky,
We’ll investigate – but please understand that this is not of the highest priority, because you’re not really supposed to be using that function. We do all that automatically via our server in all normal cases.
It’s there partly because of historical reasons, and also as a last resort for non-Internet-connected devices. But it’s used very seldom.
Do you really have a situation where you cannot let AxCrypt do this work for you automatically?
Hello Cedric,
Happy to hear it! But, in the future don’t forget to keep backups of your important data – encrypted, or not!
Hello Cedric,
The messsage indicates that the file has been tampered with or improperly saved.
It’s hard to say, but it sounds like you’re using the old unsupported version 1.x of AxCrypt.
If that’s the case, you can always try to decrypt the file anyway and ignore the error. It probably won’t work, but you can try. See http://www.axantum.com/AxCrypt/Registry.html for details, it’s the TryBrokenFile setting.
If you’re using AxCrypt 2, let us know. There’s a setting there too that you can try.
But, in any case, backups are your protectoin against data loss for all data, encrypted or not. Think if you might not have a copy of the file somewhere.
Hello Anonymous,
We are looking into this, and will be releasing a new version shortly hopefully.
Hello Anonymous,
No, not really, because it’s part of what windows does. It is technically possible to use a so-called icon overlay, but it has never worked very well and requires a lot of very specific code for Windows.
So, sorry, we don’t support that!
Hello xavier,
Where are they stored on the phone? What version of Android are you running, and what version of the mobile app?
December 7, 2017 at 11:12 in reply to: Unexpected Error. "UTF-8" is not a support encoding name. #8430Thank you Ned!
Unfortunately there’s not really anything we can do about this as I understand it, since it’s the framework that is crashing on this. Then again, it’s kind of strange that this is not a bigger problem if a major product like Sophos is defective in this way. Perhaps it’s fixed and you have an old version? Or there are other factors involved. If we could control it we could of course be tolerant of this situation, even if it is non-standard. But as I see it we can’t.
December 6, 2017 at 17:11 in reply to: Unexpected Error. "UTF-8" is not a support encoding name. #8422Hello Ian,
We investigated this error message before, and this is a message about a bad response from a request to a web server. We have checked and it’s not our server which is responding in the wrong way.
Notice the message is ““UTF-8“” is not a supported encoding name. Double double quotes. What’s happening seems to be that someone is intercepting and changing the response to send an encoding with the name “UTF-8” instead of UTF-8. The encoding name should be without quotes. The error message displays the encoding name withing it’s own quotes – so there it’s double double quotes. It’s a little meta subtle so to speak, but it’s out of our control as far as we understand the issue!
The most likely reason for this is that the user is behind some kind of firewall or other hardware or software which actually rewrites the request – and does this incorrectly. Our server is not responding with encoding name within quotes, something else is we think.
Hello Rosa,
The file is encrypted using a password. That password is apparently different than the one you are signed in with. It thus does not help to enter it again, it’s already tried. That’s why the message says you’re already signed in with that password.
I’m wondering – did you encrypt the document, or did someone send it to you?
If someone sent it to you, they need to use the key sharing feature in order for you to be able to open it. If they do this, the file is updated to include a key for you so you can open it – but they will need to resend the file to you after adding you as a recipient. All this is explained on our web page https://forum.axcrypt.net/ .
Hello Rosa,
From our logs, we can see that you downloaded AxCrypt, created an account, and set a password. Then, about 3 hours later, you signed again to the web site and among other things changed the password.
This means there are two passwords in play. Please sign out and exit from AxCrypt, then ensure you are online, sign in again with the new password and try again. If the file still does not open, please use the original password you set when you created the account.
-
AuthorPosts