[SvanteSpectator]

Hi Robb!

Thanks for your feedback.

1. Sorry, no we don’t yet support the recursive encryption of folders, due to problems caused when some users do not understand how this works. We’ll be adding an options page where advanced options like this will be possible to configure.

2. There’s no hotkey, but you can sign out quickly from the tray. You can also sign out by right-clicking anywhere almost in Windows Explorer and selecting AxCrypt | Sign Out.

3. Here we have a problem… We do not advocate this practice. Please read http://www.axcrypt.net/blog/use-of-different-passwords/ for a longer discussion about this.

[SvanteSpectator]

Hello John!

Files will not be stored in the temporary folder, if you decrypt them. However, if you open the encrypted file via AxCrypt, it has to be decrypted and temporarily stored somewhere – and that’s the location you’re seeing. When you sign out of AxCrypt, or use the red “broom” icon to clean, or in many cases when you exit the application the temporary copies will be deleted.

This is no different from how AxCrypt has always worked, with the slight modification that sometimes you do need to use the red “broom” icon. This change was forced because of other problems with keeping track of when to re-encrypt and wipe the temporaries in AxCrypt version 1.

[SvanteSpectator]

Hello Martin,

For the AxCrypt ID account, it works as usual – you can reset the password using the forgotten password link. As you realize, it won’t open previously encrypted files.

Go to the sign in page, and use the “Forgot your password? click here” link.

[SvanteSpectator]

Hello Anonymous,

While the statement about 7-zip is completely off-topic ;-) I’d still like to correct a misunderstanding here.

You are correct that CBC mode is the foundation for the typical padding oracle attack, it is rarely applicable to file encryption software such as 7-zip or for that matter AxCrypt.

The thing about a padding oracle attack is that you need an oracle. An oracle in this context, is some entity with knowledge that can be questioned. A padding oracle is something we can ask whether or not the padding is correct for a given encrypted message.

For such an oracle to exist, there must be an entity that has knowledge about the decryption key that we can ask whether or not a message is correctly padded.

Such an oracle is typically a server that has the decryption key, and that we can send a message to – and get a response back saying “Invalid padding” or something similar when the padding is incorrect.

For the typical 7-zip or AxCrypt file, no such oracle exists. You just have an encrypted file, and no server or other device you can send a modified file to with the intend of learining whether the padding was correct or not.

So, even if 7-zip and AxCrypt version 1 uses CBC mode, it is a rare situation where a padding oracle attack is possible. You need that oracle.

[SvanteSpectator]

Hi,

Good luck, and thanks for the feedback. We’ll try to make it even clearer. The “main” password is for all files encrypted with AxCrypt 2. You sign in once per session, and then encrypt and decrypt using that password automatically.

[SvanteSpectator]

Hello Martin,

What do you mean that you can’t change the password?

You can do this under the File | Options menu, like this:

If this does not work for you, please send us a screen shot of the situation.

 

[SvanteSpectator]

Hello Luke,

AxCrypt uses the standard Windows Installer technology for install and uninstall. There should be no specific issues with that.

Please send a screen shot of the error message and it might be more clear what is happening.

[SvanteSpectator]

Hello Anonymous,

What should happen is that with version 2 you sign up and create your AxCrypt ID, and set a password. This password has stronger requirements than the 8 character password you apparently used for your existing encrypted files.

What should happen is that after setting your new password, and signing in to the new version you try to open your existing files. You will then be asked for the old password. Now you enter your existing password and the file is both opened and converted to the AxCrypt 2 format *and* to use the new AxCrypt 2 ID longer password in the future.

If something else happens, please send a screen shot of the situation.

[SvanteSpectator]

Hello Pablo!

I’m afraid you are in a bit of trouble here. However, I do believe that Dropbox might be able to help you out here. See https://www.dropbox.com/en/help/11 .

 

[SvanteSpectator]

Hello,

We really need it all… And you should not post it here, as it says – email to support@axcrypt.net .

There are instructions there how to make a single zip-file too.

[SvanteSpectator]

What version of AxCrypt are you using?

If you are using version 2, please follow the instructions here: http://www.axcrypt.net/blog/send-complete-error-report/ .

[SvanteSpectator]

Hello michel,

You say “it doesn’t start”. Can you please send a screen shot of just what happens instead? Any error message etc?

Also you say you use ”mode sans échec” to get AxCrypt to start. But as far as I know, that’s a startup option for Windows, not for applications. Can you also please explain more, and if possible include a screen shot of just where you use that option?

[SvanteSpectator]

Hi Ryan!

Thanks for your feedback. Sorry to see you go, but self-decrypting/self-unpacking files are really quite evil ;-) It’s just not a good function.

We’ll instead be focusing on making the stand alone version even easier to use, so it can be used without an account.

[SvanteSpectator]

Hello Anonymous,

But that is kind of my point – with the standalone download version of AxCrypt 2, there is no need to install anything.

And, with the key-sharing functionality, you don’t even have to agree on a password with the recipient. They will set their own password and use that.

Still, we’ll be looking into ways of making AxCrypt 2 offer some of the very simple pure password-based modes of operation in the future.

[SvanteSpectator]

Hello RHF,

Thanks for your input. Can you just explain why the standalone full version of AxCrypt 2 is a less good solution than the extremely limited decrypt-only version that is the self-decrypting version for AxCrypt 1?

I’m trying to understand exactly what it is that users are looking for, so that we can find a way to provide the benefits without the drawbacks.

[Author]

Posts