Forum Replies Created
-
AuthorPosts
-
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.
Hello Natalie,
We don’t send files. We encrypt files, and share keys to files so they can be shared (by other means).
You’ll have to contact the person who wants you to send files.
AxCrypt has a key sharing feature letting you add recipients by email address, who when they receive the file can open it with their own AxCrypt password (that’s you, the recipient).
Key sharing embeds the shared key into the file. The file must thus first be key shared with the recipient, then sent or file shared (that’s the other person, the sender). Please note that AxCrypt does not share or send the actual file. To see a quick instructional video explaining how to use key sharing, please view https://www.youtube.com/watch?v=9z3KOZD-Yks .
Hello,
I am very sorry to hear that you apparently are the victim of an attack against your files using AxCrypt.
However, please understand that AxCrypt is just a tool that is used by millions of legitimate users for good purposes. I am very sad that someone would choose AxCrypt as the tool to perform such attacks.
Unfortunately in this case, AxCrypt is based on strong encryption, and it is generally not possible to crack the encryption.
What you must do is contact your local police.
Please read http://blog.axantum.com/2012/07/axcrypt-used-for-ransom-attacks.html for a longer discussion of what I know about this .
Hello Jean,
Are you using version 2.1.1526 ? This was a version that was available for about a day, which included a serious reliability issue which can cause what you describe under certain circumstances (notably, files left open when AxCrypt was automatically signed out). It was withdrawn very quickly.
If so, you would have received a pop-up message stating you must update because of this. We have a mechanism where we can flag specific versions as “bad”, either for security or for reliability. As long as you allow AxCrypt to connect to the Internet, you will be prompted to upgrade in very strong terms.
Thank you Ryan!
-
AuthorPosts
