Forum Replies Created
-
AuthorPosts
-
Hello Mike,
Happy it worked out for you, good luck!
And thanks for the support in the World Cup. But, hey, most people see it as Sweden vs. Sweden so Sweden wins in any case ;-) .
Hello Mike,
Graham makes some good points. To clarify:
The reason only password reset is enabled is because you’re not signed in.
You need to know the old password, and sign in, to *change* the password. This is the same via the web.
Hello Debbie,
this is because your file is encrypted with a different password than you sign in with. Since you’re signed in with lets say “MySecret999”, but the file is encrypted with a different password decryption fails and AxCrypt asks you for the correct password. You then enter “MySecret999”, but AxCrypt has already tried this since you’re signed in – so it tells you this that it’s no use to re-enter the sign in password. It’s already been tried and it doesn’t work.
You need to remember the password originally used to encrypt the file.
Please be aware that a password *reset* will *not* let you access previously encrypted files, that were encrypted with the password used before the reset. A password *reset* will only let you sign in, and will be used for new encryptions. To decrypt files encrypted with the previous password, you need to know that previous password.
Hello Robert,
I appreciate the feedback, and we do try to adapt as best we can. There are several design decisions involved here, not 100% sure which one(s) are the critical ones here. I do think that disallowing passwords such as ‘password’, ‘secret’, ‘123’ and ‘a’ is an indisputably good design decision.
The other decisions, such as using the sign in metaphor for deciding on what password to use by default for encryption and decryption can of course be discussed, but what you can’t know is that it’s based on actual use of the “old” model. One recurring problem with the old model with the need to re-type your password every time an encryption was to be made and the only verification done was by typing it twice was that users mistyped (twice) and then lost their data.
The sign in metaphor allows us to verify that the password used is actually the same one as was used the first time. This has virtually eliminated the data loss caused in version 1 by mistyped passwords. It has also reduced the number of instances of lost data due to immediately forgotten passwords at first time use.
Finally, the design decision involved here with sharing is not requiring the sharing of actual passwords, is also in my mind a good one. However, here we’re open for allowing password sharing in addition, since we do see some cases where this would be beneficial. We have an issue for this, you can follow it here: https://bitbucket.org/axantum/axcrypt-net/issues/131/add-sharing-password .
Hello Robert,
Sorry, but you meaning was not entirely clear about what was ridiculous ;-)
But the thing is – you then say “…just in order to encrypt a file that I want to email to someone…”. Well, provided that you do in fact care about the security of the file being sent, you must enter a password sometime.
With the old AxCrypt 1.x, in order to complete the sharing, you’ll have to agree upon and communicate that password. If you communicate with several parties, it soon becomes unmanageable. Also, each file thus encrypted will require you to know a separate password.
With AxCrypt 2.x, you “sign in” first. This then becomes the default password for encryption (and a little more, it verifies that you actually are using the right password, and not a typo).
Then, you select your recipients, identified by their email addresses to share with and add them as recipients. Each file thus encrypted will be openeable by your own secret password, and all the recipients separate own passwords – no need to keep track of different passwords, no need to communciate and/or agree on passwords. One password to rule them all!
Yes, it’s different. I think it is soo much better! But then I would, I guess, be a bit partial seeing as I am the lead developer of both the old and the new AxCrypt.
Hello Yvonne,
Please contact our support, but generally speaking – if you misremembered your password you can’t decrypt.
Also, you should *never* give your password to anything to anyone. I edited your post to remove it, but the damage is essentially already done. You should consider all your files as potentially compromised.
Hello Robert,
Thank you for your input!
To download the old, version 1, go to http://www.axantum.com/, click on the logo top left to enter the site and then to the download page. (Direct links to the download page *will* redirect to the new version 2 download page.)
I must agree with Harry on one point, when you say that it’s a problem that you “must remember this complicated password you force the user to create” that you should reconsider your use of encryption.
There’s no point in using encryption software with a weak, easy-to-guess password. It might make you feel safe, but you’re not. The point with requiring at least a reasonably strong password with AxCrypt 2 is just that – to make it very clear that a strong password is required for the software to have any effect!
On another pont I’ll disagree with Harry – has far as I know AxCrypt 1 does work with Windows 10, the latest version of Windows. However – we don’t test it, we don’t verify it, we don’t maintain it and we don’t support it.
Hello Ryan,
Thank you for the feedback. We’ll investigate immediately and release a patch version asap. See https://bitbucket.org/axantum/axcrypt-net/issues/419/rename-to-original-causes .
Hello Ryan,
No, we havn’t sorry! I’ve increased the priority and assigned so it should get fixed for the next release. See https://bitbucket.org/axantum/axcrypt-net/issues/177/let-deleted-my-axcrypt-folders-stay for progress.
Ok, so the “network drive” has been added to the Secured Folders list, right?
Hello Huseyin,
I am very sorry to hear that you apparently are the victim of a hacker ransom attack against your files.
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 a hacker has chosen AxCrypt as the tool to perform the ransom 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, and have them follow the money and Internet trail to the hacker. Since others appear to be in the same situation, you may want to contact media in order to make this problem more widely known, and also gain the possibility of a group action of all the victims against the hacker.
We cannot help, we are in no way involved, and there is no way to open the files without the passphrase used.
Please read http://blog.axantum.com/2012/07/axcrypt-used-for-ransom-attacks.html for a longer discussion of what I know about this affair.
Thank you! Now, for clarification, can you just explain during which operation this happens? There are apparently no watched folders (or did you clear them from the screenshot)?
We have opened an issue here https://bitbucket.org/axantum/axcrypt-net/issues/418/sequence-contains-no-elements-in .
Hello mehmet,
I am very sorry to hear that you apparently are the victim of a hacker ransom attack against your files.
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 a hacker has chosen AxCrypt as the tool to perform the ransom 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, and have them follow the money and Internet trail to the hacker. Since others appear to be in the same situation, you may want to contact media in order to make this problem more widely known, and also gain the possibility of a group action of all the victims against the hacker.
We cannot help, we are in no way involved, and there is no way to open the files without the passphrase used.
Please read http://blog.axantum.com/2012/07/axcrypt-used-for-ransom-attacks.html for a longer discussion of what I know about this affair.
Thank you, that helps!
Can you also add the part where we see the status line of the software, with the version and the status?
Hello taco de wijs,
Could you send a screen shot of the respective situations please?
-
AuthorPosts