Forum Replies Created
-
AuthorPosts
-
Hello Joe,
Please contact support for this by emailing support att axcrypt dott net .
Do include screen shots of the various error messages, not too closely cropped so we can see the Windows Explorer and full AxCrypt window.
Hello Greg,
Yes, technically we can add auto-anonymous-rename and we can display the real file name when signed in (what you suggest is what we do – we keep the original file name in encrypted form in the encrypted file).
Auto-add is on the to-do-list, as is another related issue:
https://bitbucket.org/axantum/axcrypt-net/issues/310/add-anonymous-rename-to-options-for
https://bitbucket.org/axantum/axcrypt-net/issues/151/add-restore-original-name
We do display the original file name in the recent files view. To do so from Windows Explorer is possible, but non-trivial because it requires some communication back and forth between the shell extension and AxCrypt, so this we probably won’t do. We might do something inside the app though to facilitate finding the right file when it’s not in the recent file window.
Hello Paul,
No, AxCrypt is a file encryption software, and only encrypts files. However, since the original file name is included in the encrypted information, the encrypted file can be renamed to anything while the original name will be still be restored on decryption. There’s also a function to do this simply called anonymous rename.
Hello Marvin,
There’s something not quite right with your description of events. The typical sequence of events are identical, but named differently. There’s no difference really between AxCrypt 1 “asking for a password to open the file” and AxCrypt 2 “requiring you to sign in to open the file”. In fact, I believe the keystrokes are exactly the same!
AxCrypt 1:
- Double click the file.
- AxCrypt pops up a dialog asking for the password.
- Enter the password, hit “OK”.
- The file opens.
AxCrypt 2:
- Double click the file.
- AxCrypt pops up a dialog asking you to sign in.
- Enter the password, hit “OK”.
- The file opens.
The one scenario where you’d be asked for a password twice, is if you’re opening a file encrypted with a different password than your sign in password, encrypted with AxCrypt 1 or with AxCrypt 2 by another user or yourself, but with a password *reset* (not *change*) between. In the case of an AxCrypt 1 file, it’s a one-time thing since we’ll upgrade the file to AxCrypt 2 and use the sign in password. So next time it’ll work as usual.
I’m guessing that “I even changed my AxCrypt.net password to my preferred encrypt code and that allows me to sign in online” is not quite correct. Our logs show a password *reset* on September 7, which would explain the “but I still must use the zxzxzxzxzx on my PC to then access my encrypted file“. If this is the case, of course you must! A simple password reset, which only requires access to your email inbox to succeed cannot restore access to previously encrypted files!
Hello,
Ok, well… If you can let the other party know, we’d of course be interested to know why they chose to remain with unmaintained software, while we are very actively developing version 2. If they contact me via support att axcrypt dott net I’d be happy to listen to how they reason.
Hello Arnaud,
Yes, you are essentially right when you say: “I could read the documents that she sends (shared passphrase) me but I could not send it to her“. The reason is that AxCrypt 2 stored encrypted data differently than AxCrypt 2, among other things in order to make the format more robust.
I suggest you ask why the other party is unwilling to upgrade. We no longer support or maintain AxCrypt 1, even if it is available still.
Hello Arnaud,
No, we don’t support multiple passwords with AxCrypt 2, and while AxCrypt 2 can open AxCrypt 1-files, AxCrypt 1 cannot open AxCrypt 2-files.
Is there any absolute reason why all parties can’t use AxCrypt 2 and the key sharing feature?
Hello,
James has initiated a support case for this. (The most likely reason for the situation appears to be that folder 1 and folder 2 were encrypted at two different points in time, with a password *reset* between but it’s an ongoing case.)
Hello Marvin,
As Euan says – we only use a single password. The value in “force a login to axcrypt to only encrypt a few files” is, among other things:
- We can strongly verify that you are entering the password you think you are entering, reducing the risk of dataloss due to a typo when you encrypt new files.
- We can keep the password around for the duration of the sign in session, making encryption and encryption – even of a few files, a much more convenient task.
- We can verify your account status, i.e. subscription plan (Free vs. Premium etc).
- We can synchronize your key pair with the local device and the server, making such things as global password change possible.
- Although we log very little, the little we do log often helps us understand why users are experiencing problems which thus allows us to provide more effective support.
There are other benefits as well, but these are some. For information about what we log, what we have on the servers and how everything works, check out the privacy policy, security information and technical information at https://forum.axcrypt.net/ .
September 8, 2017 at 10:09 in reply to: relationship between my encryption code and my login password #7798Hello Marvin,
What you’re saying does not make full sense to me.
First of all, please be aware of the difference between password *reset* and password *change*.
A *reset* is when you don’t know the old password, and only supply a new one. This is essentially a re-registration, and will not allow you to access files encrypted with the old password.
A *change* is when you do know the old password, and supply that as well as a new one. In this case, files encrypted with the old password will in fact be accessible with the new password due to the use of public key technology in AxCrypt.
Your first statement (“It has had no effect on my encrypted file on my windows system“) is consistent with you having issued a password *reset*.
Your second statement (“I decrypted the file, then reencrypted it (it never asked for a encryption pass phrase) and the file was encrypted with the old login from your website“) is hard to understand, unless you where in fact signed in with the “old login from your website” and you in the first step actually did a password *change* – but only via the web without signing out and signing in again in the app.
Can you perhaps clarify?
Hello James,
I’m sorry to hear this. But, you have made some form of mistake here. If you contact support by emailing to support att axcrypt dott net we’ll try to help you out.
Hello Alfred,
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.
Thank you Johnno!
Hello Dave,
Thank you for the feedback! We may indeed do so in the future, in one way or another.
Hello Jean,
Unfortunately, if you were using version 2.1.1526, and got the message it means the file itself is damaged. Upgrading won’t help for the damaged file(s), but will prevent it from happening again.
-
AuthorPosts