Forum Replies Created
-
AuthorPosts
-
Hello Luc,
I don’t think you “changed” your password to access your account, I think you “reset” your password.
A password *reset* (where you do not know the old one, and instead get a new verification email, and then set a new one without ever knowing the old one) of the account will gain you access to the account as such, but not to encrypted files.
A password *change* (where you first enter the old one, and then set a new one), will enable you to open your old encrypted files with the new password.
To open any encrypted file you need to know the original password, or the password that it has been *changed* to.
There is no way to reset it to open the files, or to send it to you.
Hello Marcus,
https://forum.axcrypt.net/download/
Standalone downloads
The standalone version of AxCrypt is directly executable – no installation required.
Windows 32 and 64 bit AxCrypt-2.exe AxCrypt 2 standalone / portable version for Windows
Hello,
Nothing is of course impossible in the world of software, but no – I don’t think it’s possible that this is the cause here.
You’re not going to like this, but I’m fairly sure that you in fact are not entering the right password.
What might confuse you a little bit is that when you upgrade, you’ll first be asked to set a new password for your account. Then, when you open an AxCrypt 1.x file the first time, it’ll ask you for the original password you used with AxCrypt 1 for the file. If you enter it correctly, the file will automatically be re-encrypted with version 2, and use the new sign in password for AxCrypt 2.
Dale, I did not see this before now, but it looks a little dangerous… Looks like it’ll kill AxCrypt. Since you refer to ‘autohotkey’ of which I know nothing, but from the name it seems it could send keystrokes. Can’t you write a similar script that just signs the user out instead of killing the process?
Hi William,
You write: “Nobody can then blame AxCrypt if they lose their data“.
The unfortunate fact is that this happens on a daily basis in various similar situations, most commonly forgotten passwords.
Therefore, we’ll be requiring a user to enter the password again when changing options. We’ll still be getting some angry users blaming AxCrypt when they encrypted C:\Windows…
Thanks for your input!
Hello Adam T,
It’s one of these features that are required by some users, and cause significant problems for other users. It’s on our to-do list, you can follow it here: https://bitbucket.org/axantum/axcrypt-net/issues/191/add-option-for-recursive-operation .
I can’t promise any delivery date for this, but it should not be too far off. It’s much requested and it’s not really that technically difficult – although there’s more to it than it may seem…
Hi Gary,
Yes, it’s been asked before ;-)
There’s an issue for it, so it’s on the to-do list. See https://bitbucket.org/axantum/axcrypt-net/issues/186/add-option-for-requiring-password-every .
Hello Barkeley,
First off – you don’t need to recreate your account just to install on a new computer. Just install and type your email and then your password and you’re good to go.
However, scouring our logs, I find that you’ve misspelled your own email. Look very carefully at what you’ve typed, and you’ll see that you have mistyped the fifth letter. You typed an ‘h’ instead of an ‘s’.
That’s why you’re not getting any verification emails most likely. Apart from the fact that if you type the right email, there’s no need!
Hi Paul,
Thanks for the feedback. Also Lucas, thanks for your comments.
About the interface – you don’t need to see it. Just minimize it and then use AxCrypt from Windows Explorer like you always did. It’ll stay minimized the next time you start it too. The “Enter Password” dialog looks a little different, but is actually cleaner than version 1 – which includes 2 checkbox options ;-) For regular encrypt/decrypt/open use, there is virtually *no* difference in the number of clicks and keypresses. It *is* the same! (In other words, the “Simple Interface” mode is one minimize click away).
Also about the interface – through the years, a common feature request has been an install-free portable version. I.e. a version which does *not* use Windows Explorer context menus and double-click as the main way to use. In order to do this, a user interface of some kind is required! Now, we can discuss the user interface chosen. But for a portable version to be possible, an interface is needed. AxCrypt 2 can be run in portable mode. Feature request: Check.
About the online/offline – yes, part of it has to do with commercial reasons, we need to keep track of who is who and who has paid. That’s fairly standard. But, more importantly, it allows us to move into a more modern world of public key-based cryptography for sharing – with unparalleled ease use. We feel that it’s worth it. When we have the resources we’ll probably try to develop pure offline version.
About happily paying for the 1.x – there’s always been an option to donate. If only 1% had happily donated, development of that would probably have continued. If I had made the mistake of moving from voluntary donations, to required licensing – it would have completely killed AxCrypt. Plenty of precedents. There is nothing that will stir up annoyance like when a FOSS simply goes and becomes commercial and you can’t have it for free any more. So, the only option was to redevelop a new AxCrypt, keep the basic same features free – and *add* Premium functionality. Now, you can still have AxCrypt for free, and it’s still open source. But, many will now find an incentive to pay for the premium stuff – which allows us to develop it and this benefits the free users as well. So, it simply isn’t as simple as it may look.
A Windows Phone version is actually not that impossible, but it does depend on funding. The technology we use make it if not trivial, at least, feasible to do.
Finally, AxCrypt 1.x has not changed in any essential way in 15 years. It’s time to mess with ;-)
Hello,
As the message you quote say – we do not delete accounts on request. You must delete it yourself. This is for your security.
Sign in to your account and delete it at https://account.axcrypt.net/Home/Login .
If you do not know the password, issue a password reset at https://account.axcrypt.net/Home/PasswordReset and then sign in and delete it.
If this does not work, please send a screen shot of the error message describing your problem.
February 6, 2017 at 22:20 in reply to: Simply Password Protect (encrypt) of a file to be shared? #5429In this case, I’d suggest using a functional non-personal account as the ‘master’. Anyone with access to that account, would have access to the file.
We will be introducing key recovery for business accounts in the future but in the meantime, the above is a simple and effective work-around.
Thanks, Miguel!
February 6, 2017 at 20:05 in reply to: Simply Password Protect (encrypt) of a file to be shared? #5424Hi,
Here’s how AxCrypt works with sharing. We have a function called ‘key sharing’ which means that you can embed an encrypted key to the file to any other person(s).
They will then open the file with their own password. No need to share passwords. You just add that persons email address to the list of persons who should be able to open the file, and they can.
Check out our videos on this at https://forum.axcrypt.net/ .
February 5, 2017 at 15:51 in reply to: Unexpected Error! Exception during processing Access to path 'C:\xxx' denied #5413Hello Gary,
Just for completeness sake – I would like to point out that AxCrypt Premium (not free, sorry) does include a properly encrypted online password manager that you can access from anywhere.
February 4, 2017 at 21:45 in reply to: Unexpected Error! Exception during processing Access to path 'C:\xxx' denied #5407Hello Gary,
I’d really like to suggest that you don’t encrypt program executables in %ProgramFiles% . There’s a reason why you’re running into trouble, and that’s because Windows is trying to help you not make a mistake.
There should be no reasonable reason for you to encrypt anything there.
-
AuthorPosts
