Forum Replies Created
-
AuthorPosts
-
August 9, 2018 at 12:41 in reply to: AX 1.7.3156 Failed to startup. Faulting application path. #11021
Hello Milan,
Glad to hear you got it working again, so it was what I originally thought it was. Good job. I seem to recall that there were some versions of Adobe Acrobat that caused the problem after installation…
As for your reasons of not wanting to upgrade, I appreciate you taking the tine. The first issue – that others will have to upgrade as well, can’t do much about that. If that was a universal principle, no software could ever evolve. You’d still be stuck with Word 1.0… So, yes, I recommend both you *and* your colleagues to upgrade!
The second reason, we do use the email address for several vital functions. One of them being solving the problem of sharing files with others. We use modern public key cryptography in a very simple package to enable sharing of files with others without sharing any passwords. So, AxCrypt is also a key server – and this is a normal cryptographic function, and it does require some form of identification moniker. We choose to use the email address because we don’t consider this to be a secret, and we also specifically state that using AxCrypt itself should not need be kept secret. We don’t try to hide the fact that an encrypted AxCrypt file is encrypted with AxCrypt. AxCrypt is strong enough so it will not matter.
Part of it is definitely about business! I’m happy to year you’re willing to donate, unfortunately not one in a thousand of the free users of AxCrypt will do so, and even you have not done so yet apparently except when this came up. So, the freeware donation model just did not work. I had the choice of sunsetting the whole project and shutting down, or trying to find a model where I could get some return for the time and effort spent.
I do understand that there is a natural resistance to change, but sometimes things will just have to. With AxCrypt 1 and 2 this is the case.
Of course you’re welcome to continue using AxCrypt 1 for as long as you like, or use AxCrypt 2 for free too. But, as time goes by, you’ll be more and more exposed to risk using old, unmaintained, unsupported software.
August 9, 2018 at 07:59 in reply to: AX 1.7.3156 Failed to startup. Faulting application path. #11019Hi Milan,
Thank you for the information, but this is the point where I will have to say what you don’t want to hear…
Upgrade to version 2.
As mentioned, we don’t support and we don’t maintain version 1.7 anymore. It’s old. Things around it changed. It could be something in Windows 10 (although I’m not sure about that either). But, this is what happens with software, and why it needs maintenance. Which we don’t do for 1.7…
Perhaps you can tell us just what the critical reasons are for not using version 2?
From what I understand you can at least access your files now, so there is no risk for data loss at this point.
August 8, 2018 at 13:45 in reply to: AX 1.7.3156 Failed to startup. Faulting application path. #11017Hello Milan,
There may also be locking of files involved. Have you rebooted (as you should also have been instructed several times during uninstall / install process)?
The error message stems IIRC from AxCrypt trying to clean up it’s temporary folder (which it does during startup as well).
August 7, 2018 at 13:50 in reply to: AX 1.7.3156 Failed to startup. Faulting application path. #11015Hello Milan,
Please install the current 2.x version. ;-)
Ok, seriously. The thing is, we don’t support or maintain version 1.7. In your case, though, since obviously AxCrypt has not changed – something else has.
In this case, probably the location or permissions for the %TEMP% folder in Windows, which is where AxCrypt stores it’s temporary files.
Hello Mark,
As you say – that’s not how it’s supposed to work, and something is definitely wrong if what you describe is what is happening.
There are a few cases where the offline / online password can get a little out of sync, but that only happens under specific circumstances and only when changing or resetting passwords.
Can you:
1) Please follow the instructions here: https://forum.axcrypt.net/blog/send-complete-error-report/ and send the result to support at axcrypt dot net, and mention it’s for me.
2) Start AxCrypt in normal online mode, use the “clear all settings and exit” option. Restart AxCrypt. Re-enter your AxCrypt ID email and password, sign in, verify it all works and then try the “always offline” option again.
Step 1) is to have information to analyze to try to determine the cause of the problem. Step 2) is to verify that offline actually does work. It does not fix the problem if there is one, causing you to get into that situation, but that’s what step 1) is for.
Hello Liz,
Always download the current version available via our home page, https://forum.axcrypt.net/ on the download page there.
Hello Larry,
As mentioned elsewhere, this is because you don’t have an email with gmail.com and comcast.net . Your email is with yahoo.com .
Hello alan,
Can you please provide more details? If the problem persists, perhaps you might want to contact our support.
Normally there should be no trouble like that, regardless of whether you have Internet access or not.
Hello Larry,
It seems there’s more to the story! You’ve tried to sign in with three different email address (the same first part) at gmail.com, comcast.net and yahoo.com .
The reason for the gmail.com and comcast.net email not arriving is simply that you do not have an email with that address at gmail or comcast. Sorry, but not even we can send email to a non-existing email address!
It also seems that your sign-up with the yahoo.com address worked fine without trouble.
Good luck, and I hope that you’ll reconsider your recommendation to friends, but do tell everyone that it’s important to enter the right email address, one you actually can receive email to!
Thank you!
But… Now it does look like the file is in fact encrypted in it’s original location!? Or did you move it out of the folder, encrypt it, and then move it back again?
Hello Calisson,
Once again, thank you for your efforts to give us this detailed information. We’ll see if we can figure it out ;-)
Could you give us the full path to the file in question (I don’t think there’s anything sensitive there)?
Hello Calisson,
Final (?) question… When you say ‘move’, is that literally moving the file? (there’s a difference…) Or do you copy it? And, most importantly, do you change the extension from .bak?
Hello Calisson,
Thank you very much for that information! We’ve logged a bug for that here https://bitbucket.org/axantum/axcrypt-net/issues/427/cant-encrypt-sql-server-backups-in .
Some follow-up question. Just exactly how does not work in the original location? I know you write at the top about connection refused etc, but I really don’t think that’s what’s happening.
Can you describe just what happens when you try to encrypt the file in it’s original location?
Hello Joy,
Go to http://www.axantum.com/ and then click the shield logo in the upper left corner. This will get you the menu and there you chose Download.
Hello Anonymous an Alec,
Concerning “Is it possible using settings to make sure that the temporary unencrypted file is created on the user’s local PC so that it is never on Google drive in clear?“: This is exactly how AxCrypt works. It never decrypts any file in the original location (and it doesn’t work directly with Google Drive either, it only works on the local hard drive synchronized/streamed copy). It always decrypts the file temporarily to a local temporary folder, and then re-encrypts it to the original location.
In the case of synchronized/streamed cloud service folders, the plain text file can only hit the remote cloud server if the file is created there in plain text. And then only if the time window between creation and initial encryption is long enough. To be 100% safe – always encrypt a new file before actually making it available for sharing via a cloud service provider. Once it’s encrypted, it’ll never be decrypted so the cloud service provider sees it, unless of course you actually decrypt it in place. But just opening the file via AxCrypt is 100% safe in this regard.
-
AuthorPosts