[SvanteSpectator]

Hello Laurent,

You seem to have two different problems here. The first one sounds strange, there is no difference between Trial Premium and paid Premium. (You do need to sign out and sign in again after purchasing to have AxCrypt update the status though).

The second one is about how it works. The only time we send an email in the key sharing scenario is when the recipient does NOT already have an AxCrypt ID account. In your case, it seems he/she already does, since you explicitly state that it’s a free account. That’s fine.

You need to add the recipient in the key sharing dialogue, and save the result (and then if it’s OneDrive, wait for it to synchronize, since the key sharing is actually added to the file, thus modifying it).

[SvanteSpectator]

Hello Christine,

Jack is entirely right. That’s just how computers work. However – we do send an email to your accountant if he does not have AxCrypt installed when you do the key sharing with him/her as the recipient inviting him/her to download AxCrypt and set the password.

[SvanteSpectator]

Hello Ted,

As Jack says, this should work just like you expect it to. If you double-click to open, it will indeed be re-encrypted when you close it.

If you’re using secured folders, you can decrypt the files there and they will be re-encrypted as well when the program closes.

[SvanteSpectator]

Oh, sorry, I kind of assumed this was version 2 all along… Glad it all worked out.

[SvanteSpectator]

Thanks Jeff!

Good point there, and we’ve received similar feedback before. We should probably pop up a progress dialog for this situation.

[SvanteSpectator]

Hello Jeff,

 

Since it’s such a large file, I don’t see that you should open it and decrypt it using double-click, right?

I would place it on a drive where there is space to keep both the encrypted and decrypted file, and then right-click the file and select AxCrypt | Decrypt . It will then only use space in that folder.

[SvanteSpectator]

Hi Ted,

It’s a limitation right now – it’ll create it if it’s not there.

As a work-around – can you not just let it remain there, empty?

[SvanteSpectator]

Hello Freek,

Sorry for the inconvenience! It’s a bug in our system, we’ve logged it and will fix at asap. Some legacy accounts have passwords that do not pass the current minimum password policy, and the problem here is that we erroneously validate the password against a policy of minimum 10 characters.

[SvanteSpectator]

Hello BASHIRU,

If you do not remember the password to your old account, you can always reset it. This is not a way to recover encrypted files! It’s only to allow you to sign in to the new AxCrypt. The new password will be used to encrypt new files. Go to https://account.axcrypt.net/Home/PasswordReset to do this, or you can also go there from AxCrypt with File | Options | Password Reset .

 

Unfortunately, if you do not know the password you cannot open an encrypted file. That is what AxCrypt is made for!

Please check the FAQ at http://www.axcrypt.net/support/faq/ for more information.

[SvanteSpectator]

Thanks Rob!

[SvanteSpectator]

Thanks Igor!

[SvanteSpectator]

Hello Bill,

Please do not send the same question to many places! It wastes our precious resources. (You already sent this to support, and we already responded).

[SvanteSpectator]

Hi Rob,

Yes, each sub folder has to be handled separately. We don’t yet support subfolder securing or encryption.

[SvanteSpectator]

Hi MMartin,

Thanks for the feedback!

Mac-version is coming up. Possibly a Linux-version as a recompile/port of the Mac-version.

Nested algorithms – probably not from us, but we do support plug-ins for algorithms…

OpenPGP-support is always on the radar in various ways, so it might indeed happen to some extent anyway….

We’ll probably stick to file encryption for some time anyway though. Virtual containers is a different game.

[SvanteSpectator]

Hello Rob,

AxCrypt does *not* split files. There is no limit except available storage concerning file size.

AxCrypt will use a digit suffix (but not quite like you’re showing) in certain situations when there’s a file name collision but that does not seem to be the case here.

If you have a file named “MyVirtualDisk.vhdx”, and you encrypt it, you will get a file named “MyVirtualDisk-vhdx.axx”.

Are you sure you’re using AxCrypt ;-) ?

[Author]

Posts