Forum Replies Created
-
AuthorPosts
-
Hello Ray,
That’s a false positive, or as I’d like to call it irresponsible defamatory, slanderous, libellous and malicious. Get a refund for your “anti-virus”. The makers of anti-virus software will flag anything, from anyone, for any reason and will never ever take responsibility for their actions.
All of the above is dependent of course on that you have downloaded the correct software from our site, and that it’s digitally signed by us, “AxCrypt AB”, and not just any file named AxCrypt-1.7.3180.0-Setup.exe, but the link does appear almost ok although it can’t actually be used directly as a link. You will be redirected to the new download site. If you go to http://www.axantum.com/AxCrypt/Downloads.html and download it, you’ll get the correct file.
Hello stephen!
Not if you *change* the password, i.e. sign in to the account, and use settings and *change* the password by first entering the old and then the new.
Our logs indicate that it was indeed a password *reset* that was performed, not a password *change*.
If you *reset* the password, i.e. request a password reset link without signing in with your existing password, then any files previously key shared with you will become inaccessible to you using the new password. If you think about it, this makes sense both from an intuitive security point of view, as well as from a technical encryption point of view. If all that was required to decrypt a file was to gain access to an email with a password reset link, AxCrypt would not be very secure, and not really be an encryption software but rather an access control software.
So, yes, the sender will not only have to re-send the file but re-key share it so it will use your new AxCrypt ID to do the sharing, and then re-send it.
Hello Joe,
Nope, AxCrypt does not even contain the string “aep”, so there’s no way AxCrypt could have done that in the first place.
However, your sample file name “File Name.pdf-aep.axx” tells a different story.
This looks like a PDF file that was encrypted with “Advanced Encryption Package“, causing it to be named “File Name.pdf.aep”, and subsequently it has been encrypted once again, now with AxCrypt, causing it to be named “File Name.pdf-aep.axx”.
So, when you decrypt the file, it’ll once again become “File Name.pdf.aep”, i.e. successfully decrypted by AxCrypt. A PDF-file encrypted with “Advanced Encryption Package“.
The “File Name.pdf.aep” will of course not be recognized by AxCrypt or Acrobat, but presumably by “Advanced Encryption Package“.
Hello Joe,
Looking at https://fileinfo.com/extension/aep it seems you might have confused AxCrypt with some other software called ‘Advanced Encryption Package’. Does this ring a bell?
Hello Mike,
The recent files list is stored in a regular text file in the folder %localappdata%\AxCrypt . You can always check if it’s still there, it’s named FileSystemState.txt, and you can open it with Notepad or any other text editor to inspect it.
Not sure, but possibly, if you *reset* your Windows password, or re-install Windows, it might become empty. We encrypt the clear text file names in the recent files list locally using a Windows encryption facility that is tied to the Windows login account.
Hello Jim,
Keeping the original file date and time is just simply wrong, and actually causes problems.
When you encrypt a file, it is transformed into something else. It’s not the same file. It should have the date and time of the transformation.
When you decrypt a file, it will have it’s date and time restored, since then the file is back to it’s original form and then it makes sense to restore the date and time as well the file name etc.
The problems caused include backup and synchronization software stopping to work. Many such softwares have “last time run” marker, and will only examine files that are newer. If we made encrypted files have the original un-encrypted file date and time, this strategy stops working. It has happened. There are other issues too.
Finally, we are encrypting files i.e. hiding information from view, and allow you to rename the encrypted file names as well. If we kept the original date and time, that would leak a little bit of information about the original file.
But, mostly, it’s just fundamentally wrong to transform a file and keep the original date and time of change. It’s changed. So its timestamp should change. If the information inside is unchanged (which it is in this case), that should be kept in meta data inside the file (which AxCrypt does).
Hello Jim,
There are two reasons this feature is not enabled by default:
1) Experience from supporting millions of users, show that this causes more problems than it solves. Non-sophisticated users wind up encrypting much, much, more than they intended often causing real problems with other applications. More sophisticated users, like yourself, are much rarer but in most cases figure it out by themselves like you appear to have done. We can’t both have it as default and not have it as default, so we’ll have to go with the option that causes least problems and satisfies most users.
2) Since the feature is Premium feature, having it enabled by default would cause the application to change behavior in a subtle and non-obvious way when switching between Free and Premium, also causing support issues. Now at least a user has to enable it manually and thus be aware of the different behavior, and if it stops working when reverting to Free, a user will have a better chance to realize the cause.
Hello Jim,
We’ll try to reproduce this, it has to do with how Windows sets up these library folders. AxCrypt should not have a problem with non-existing library folders.
Thank you for sharing!
Hello Steve,
The mobile apps require a paid plan. If you are not on one, we’re offering you a free trial. But you cannot use the mobile apps without either a Business or Premium plan.
Hello Nadir,
Have you been using AxCrypt for some time perhaps Nadir? My guess is that the files you can’t open are time stamped at some certain time where you might have mistyped your password using AxCrypt 1 – or before a password reset if you’re using AxCrypt 2. Please contact support for more detailed help, since we can’t tell just what your AxCrypt ID is (if you have one) from the forum post.
Also, what is not cool about charging a small amount of payment for providing software and services? In this case password management. You’re free to try it for a month without any cost. If you don’t like it, don’t use it. If you do like it, you’ll have to subscribe.
Hello Macaroni,
AxCrypt is really a very simple program in many ways (although complex inside regarding the crypto).
It does not do anything magic or particular with files. It encrypts them, making for example “Document.docx” become “Document-docx.axx”. It then also manages the process of opening and saving them in a relatively simple manner.
When properly installed on a computer, it will associate the “.axx”-extension with AxCrypt, enabling the right-click menu and double-click functionality.
The most common reason for this being broken is the user not fully understanding Windows file association, and reasons “I want this to open in Word, I will tell Windows to open it with Word”. There are many ways this situation can arise, but it’s the most common situation.
Another case might be when the user has downloaded the stand-alone “portable” version and never actually installed AxCrypt via the installer, which is required for Windows to be properly configured regarding the right-click menu and double-click.
The “file is in use” is most commonly caused by it being in use, often for example by the Windows viewer which refuses to release files. The cure is often to actually exit the program where it is open, not just close the document/file.
AxCrypt works well with most if not all anti-virus software, since it doesn’t do anything strange. It is in many ways very similar to compression and archive software such as WinZip and similar.
March 20, 2018 at 21:42 in reply to: Axcrypt2 (not Premium) file reverts to earlier saved version when archived #10132Hello Bryan,
I think I know what is happening. AxCrypt 1 and 2 works very similarly, but the big difference is how/when an edited file is re-encrypted.
What happens when you open an encrypted file is that it is decrypted to a temporary location. This is the same for v1 and v2.
At this point, you have two copies of the file – the original encrypted file, and the decrypted file in the temporary location.
What you now seem to do is do perform a ‘Save As’, probably to the location of the original encrypted file, and then close it.
Now, with v2, it thinks it knows that there is a decrypted file in the temporary location, which corresponds to the encrypted original file.
You, now, move the original encrypted file to your archive spot, and then rename the updated file to have the same name as the original encrypted file.
AxCrypt is now effectively fooled, and has indeed lost track of what is happening.
You are making this overly complicated I think. A much easier procedure is just to whenever you want to archive a version of the encrypted file, copy it to the archive location. Windows will even suggest a versioned file name for you if there already is a file there with the same name. Done. No need for renaming, and AxCrypt is not tricked by the file rename-shuffle, and you do not need to to the Save As maneuver.
Hello njeuguet,
Unfortunately, if you do not know the password for an AxCrypt-encrypted file you cannot open it, even if you can sign in to the account. This is by design, it’s just this situation that AxCrypt is made for and it works like this even if you actually are the original owner of the file.
Please check the FAQ at https://forum.axcrypt.net/support/faq/ for more information.
Hello Shawn,
We do have the progress indicator if you have the main window open. It’s not shown as a “popup” when you use it from Windows Explorer, like in 1.x since we now do have the full user interface as well.
-
AuthorPosts
