Forum Replies Created
-
AuthorPosts
-
Hello Charles,
Sorry, no not really. Please see https://forum.axcrypt.net/support/faq/#forgot-password for more information.
Hello Alberto,
One possibility is that you misspelled the email, so do check that.
Otherwise we can check if you contact support if it has been properly sent and accepted by the recipients email server.
Finally, the user can trigger a re-send by registering manually at the web site, https://forum.axcrypt.net/ . Of course – if you’ve shared the file with the wrong e-mail address the user will not be able to open the file anyway.
Also, please remember – we do *not* send the actual files, it’s not quite clear from your post, but you do need to send the actual files separately yourself.
Hello Piotr,
Have you read the entire thread to which this post is a part?
AxCrypt works by temporarily decrypting files to the location you point out. These files have to stay decrypted until AxCrypt knows that they are no longer used by you. Sometimes AxCrypt can do that automatically, sometimes you need to tell it. You do this by clicking the “Broom” icon, which should be red when there are files in the temporary location.
If you click the broom icon and nothing happens, this is probably because the files in fact are still open in an application – or that application is still open (even if the file is closed).
Hello DSG,
No, not really, and it’s not a good idea for security. If it’s about licensing restrictions, that’s a different area.
In neither case is AxCrypt something that can be used. Sorry!
Hello Nikki,
As it turns out Microsoft has updated how EFS-encrypted files are displayed in Windows 10. Instead of green text, they are now displayed with a little yellow/golden lock icon overlay. Which is exactly what I see in the screen shot!
So, this is indeed a case of the files being encrypted with EFS. You’ll have the same problem probably opening the unencrypted PDF-files in the folder. This is not an AxCrypt problem, you’ll have to ask the person who mistakenly used EFS to encrypt the files to decrypt them.
Hello Givanni,
You obviously have a good understanding of the underlying technical issues here, so thank you for a relevant discussion.
I am now considering (although I am loath to add options and dialogs that many users will be confused by) adding a warning and an option to cancel an ongoing operation. There are still edge cases though.
It’s not reasonable to stop a person from opening an encrypted file, or encrypt a single file, while a larger background operation is in progress. The ongoing process can be time consuming because of the size of a single file, or because of the number of files, or both.
I will think about this… Thank you!
September 6, 2018 at 07:50 in reply to: With Business, do each user have to download Axcrypt to their desktop #11184Hello,
Yes you have it just right (although the 2nd user can download AxCrypt beforehand as well, and use it either in the free version, or for 30 days Premium trial).
Hello Giovanni,
Thank you for your feedback. Your scenario description sounds fairly likely to be what happened.
I am sorry if you have lost data, but I must object a little at focusing on the operations performed here. We warn you many times, and force you through a procedure where you must enter the password at least three times – all in order to ensure that you are really aware that you really need to know the password.
It is also essential to understand that one should never experiment on live data without backup. Here we should perhaps be even more clear, and have yet-another-popup pointing this out. Always have backups! Regardless of encryption or not.
Now to the heart of the matter. What should AxCrypt do when a background operation is in progress, and another one is started? I can agree in principle that a later operation that negates a pending operation can be optimized away. However, technically it gets complicated. We don’t expand the list of all files until necessary, and it just get’s pretty hard.
We could simply forbid two batch operations going on at the same time, but even that gets complicated. The whole idea of doing things in the background for long running operations is that the user can continue to do other work.
I just don’t know. Also, it’s the first instance of this scenario that I’ve heard of since we launched AxCrypt 2, so it’s not a common thing.
I think doing a quick-fix here is going to do more harm than good. We do have other registered issues about making the progress more clear, now it’s a little unobtrusive. That could help in this kind of scenario.
Hello Pierre,
Just use ‘File | Exit’ to exit, or ‘File | Sign Out’. Some more background information is found here: https://forum.axcrypt.net/support/faq/#why-password-only-on-sign-in .
Hello,
AxCrypt 1.x is deprecated, unmaintained and unsupported. Only version 2 has the sign in / sign out metaphor. With AxCrypt 1 you can check two options when entering the password – “remember this for decryption” and “remember this for encryption”. If you uncheck them, you’ll have to enter the password every time you do something. This is a bad idea, especially the “remember this for encryption”. Despite the dual verification entry of a passphrase for encryption, mistakes happen with data loss as a result. AxCrypt 2 removes this risk and is thus safer to use in this regard (as well as in all other regards…).
I really recommend that you switch to AxCrypt 2. It’s still free for equivalent use as AxCrypt 1, and is maintained and supported, and both more secure and safer to use.
Hello Rudy,
Please check out our instructional videos at https://forum.axcrypt.net/ .
Hello Andy,
Please follow the instructions here: https://forum.axcrypt.net/blog/send-complete-error-report/ and we can investigate this further.
Hello William,
I understand your situation, but think about it logically. You write “I encrypted a new file with the same passphrase and it dycrypts with not problem” and then “All other files from three years ago to the one from last week all have the same problem“.
You also say that you’ve not changed the software (and I should add, there are no reports at all of any incompatibilities between AxCrypt versions that would cause this kind of symptoms).
My conclusion really has to be that the passphrase you used for the new file is in fact not the same passphrase as the one used three years ago. All this assuming that the message you’re getting is really AxCrypt saying that the passphrase is wrong. Just to ensure we’re talking about the same thing, you might want to send a screen shot of the error dialog.
Do consider that spaces are significant, as is upper/lower case.
Hello Wahl,
If AxCrypt says “Access Denied”, that’s because Windows does not allow your user access to the files. There are many reasons why this may happen, but they are not to do with AxCrypt. Please Google and check NTFS file permissions and possibly also EFS Encrypting File System to determine what the cause may be. It may be as simple that you need to take ownership or give permissions.
Hello Javier,
If the file does not end with .axx, one of two things apply:
1) The file is not in fact encrypted with AxCrypt.
2) You, or someone else, renamed them.
If you have tried to rename them, and they still are not possible to decrypt with the message “not an AxCrypt file”, then… situation 1) appear to apply. The files are not encrypted with AxCrypt.
You can also contact support and send screen shots of the errors and possibly a sample file.
-
AuthorPosts
