Forum Replies Created
-
AuthorPosts
-
Hello Marcin,
It’s actually a limitation right now. AxCrypt does not work conveniently with multiple accounts. You’re signed out when you sign out – but you’re still connected to the same acount, and there’s no simple way to switch accounts.
For now, the workaround is to use the “Clear All Settings and Exit”, and then enter the other account – OR create two different Windows accounts – one for your work and one for your private user. This actually has many other advantages and is the recommended way, and is one of the reasons we have not put a high priority on multi-account use of AxCrypt.
Hello Curious,
The Premium plan is per account, on any number of devices. So, if you plan to sign in using the same AxCrypt ID email on all 4 computers, you’re good to go with just one Premium plan.
Other family members, if they wish to have their own accounts, must use their own plans though.
Hello Jed,
Maybe I was not clear enough. Paste would only be disallowed in the password verification field when setting a new password. Not in the first field even then, and not at all when signing in or using a password to decrypt a file.
We also do show the password by default when setting it, but it can be deselected if there’s a shoulder surfer around.
Thank you Jed!
I’ve sent Martin the brute force software link via support.
Some softwares disallow “paste” operations for passwords. We should perhaps do this for one of the fields when setting up the password the first time.
Hello Curious,
An AxCrypt-encrypted file is just that – a file. It’s like a Word-file, or Excel-file, or JPG-file or whatever. A file is a file. It’s a container for some information in a format that a specific application can interpret and do something you expect with.
So, yes, you can back them up. Or do just about anything with them that does not modify the content. You can back them up, copy them, send them via email, put in a cloud service or whatever. You can put them inside zip-archives or other archives.
As long as you can restore the file just as it looked after being encrypted by AxCrypt, i.e. unmodified, if you know the password and have AxCrypt you can open it or decrypt it.
Hello zippy,
The public key is something that belongs to the recipient. When you enter an AxCrypt ID email-address to key share with, AxCrypt contacts our server and requests a download of the recipients public key. This public key is a 4096-bit RSA key.
When we encrypt the file the following happens:
- We generate a random non-user-visible encryption key of 128 or 256 bits as the case may be, we call this the “file master key”.
- We encrypt the whole file using a key derived from the “file master key”
- We encrypt the “file master key” using your password, and add it to the encrypted file.
- We encrypt the “file master key” using the recipients public key, and add it to the encrypted file.
When the recipient recieves the file and tries to open it, the following happens:
- We try decrypting the “file master key” using the users sign in password. This will fail unless you happen to use the same password!
- We try decrypting the “file master key” using the users private key (the other half of the key pair, we keep this secret and encrypted using the users password). If the file was key shared as above, this will succeed.
- If we now have a decrypted “file master key”, we can proceed and decrypt the actual file.
All of this is an extremely simplified version of all the actual operations that take place, but it explains the overall process.
Hello Martin,
We can’t recover the first password, or any other password.
Once the files are encrypted, nothing really happens to them so they should open today if you’re providing the right password. We have only one sign in from you on that day before your vacation, so it seems you did not in fact enter the password more than the three times that are necessary for the sign up process.
There are also several layers here – when you tried to sign in today, and failed, you issued a password reset. Then you can sign in to the app and the account. When you try to open a encrypted file, that was encrypted with the old password, you’ll get a prompt for a “file password”. Now you get a new chance to enter the right password. If that doesn’t work either, the chances really are that you either wrote the wrong thing, or you’re misreading it now, or you mistyped originally.
It seems very unlikely that the two quite independent processes of signing up and setting a password for the account, and then encrypting files using the password just set, would err in the same way at the same time for one single user. We have very, very many users who do this every day.
Occams razor applies here, I’m pretty sure you’re not entering the same password as you did originally. Sorry, I know you don’t like to hear this, but…
I suggest you try to consider just what could have gone wrong with the password typing / noting down / reading back process – and try to adjust for that.
Thank you Ray!
Hello Robert and Fred,
I’m afraid the password requirements are not going to help with a brute force attack, at least not much. The easy summar is, at least 8 characters, and “sufficiently” complex.
What we actually do is more advanced. It has to be at least 8 characters. First we filter out the 1000 most common passwords when judging the strength (so “Password1234” is equivalent to no password at all). Then we calculate the “entropy” in bits of the password. Simply put, we do this by attempting to compress the password, and count the resulting bits, and then we have a lower threshold in bits where we won’t accept it.
If you actually think you almost know the password, let’s say you’d just need at most a million guesses, then it’s feasible if you have a good computer and some time. We have a simple tool to assist you in this case. Please contact support att axcrypt dott net if you need this tool.
Thank you Fred!
That’s about how it is. We’ll get there, but not immediately. Or, someone from the community pitches in. The source is after all open and available.
Hello John,
You may want to try to close the actual application that the file was open in. Or you can just exit and restart AxCrypt, that should also work.
If I misunderstand, please send a screen shot of the situation, it often helps clarify things.
Merci, Henri!
Hello Norman,
Thanks for mentioning this. It should of course delete empty folders as well as a convenience. I’ve opened an issue for this: https://bitbucket.org/axantum/axcrypt-net/issues/392/secure-delete-does-not-delete-empty .
Hello Anonymous!
That version is over 10 months old, it was released on December 15, 2016.
If you’re evaluating software, regardless of from where, you’ll probably get best results using updated software.
Your application should inform you of a new version with the ‘red lamp’ icon.
The current version is 2.1.1541 and is available at https://forum.axcrypt.net/ .
Please try that and see if you might have better results!
Hello Anonymous,
Just what version of AxCrypt are you using?
AxCrypt should keep these folders clean, and we cannot reproduce this.
-
AuthorPosts
