[SvanteSpectator]

Hello Biondollilo,

When you use the “Key Sharing” feature, and enter the recipients e-mail the file is NOT sent to them. You still have to send the actual file. When they receive the file, they will need to use AxCrypt 2 to open the file.

Regards,

Svante

[SvanteSpectator]

Hello Matt,

Sorry! No, we have not yet implemented a full command line API. Since the new AxCrypt is much easier to develop, we’ll probably do this via a separate command line version. It’s on the agenda!

Or, if you’re a C# developer, it’s not that hard to roll your own. The source is available after all!

[SvanteSpectator]

Great! I thought you had just downloaded the 2.1.1403, that’s why I was curious. On the 29th, that was the current version. 1404 was released yesterday.

Your little ‘lamp’ icon in the top right should have turned red though and informed you there was a new version available.

[SvanteSpectator]

Hi! Ok, please let me know.

Also, is it a typo, or did you get hold of 2.1.1403 ? The current version is 2.1.1404 .

If so, where did you download 2.1.1403 from?

Our official, and the only official, downloads are from axcrypt.net, for example http://www.axcrypt.net/download/ .

[SvanteSpectator]

Hello Horst,

There’s absolutely no reason it should consume any CPU at all when not working. We’ve not seen that at all.

Can you please let us know more about when this happens? For example, if you exit it, restart and sign in – does it happen then?

How many (approximately) files do you have in the ‘recent files’ list?

This is by no means by design, and if we could learn more we’ll absolutely fix it as soon as possible.

[SvanteSpectator]

Hello Bob,

I’m not at all sure I understand the situation you are in. Can you please take a screen shot and upload to show the verification dialog in question?

Svante

[SvanteSpectator]

Hello Herman!

Easily fixed.

Ensure you have the lastest version of AxCrypt 2 (2.1.1403 or later).

Ensure that you have checked the File | Options | Auto Convert 1.x Files option.

—

Because AxCrypt 2 has stricter password requirements than AxCrypt 1, and because some users have different passwords for different AxCrypt 1-encrypted files, the new AxCrypt 2 Sign In password is often different that the previous.

This means AxCrypt has to ask after it when it’s needed.

If you’ve done the above, this is a one-time affair. After the files are converted and upgraded, they will use the new password, and you will only have to sign in, thereafter all is as before.

The “empty key password which can be skipped” has always been there! This is how the previous login looked like:

Notice the Key-File field. Just ignore as you always have! You’re not the first to have troubles with the key-file field, so the next version will hide it behind a “More”-button.

Once you have upgraded and converted your old files, I’m sure  you’ll find AxCrypt 2 even easier to work with!

[SvanteSpectator]

Hello,

You must have read the old documentation (or we’ve made a mistake in the new). AxCrypt 2 does not support self-decrypting files at this time.

However – if you encrypt the file, key share it with the recipient with the Key Sharing feature you can send the encrypted file along with a link to https://account.axcrypt.net/Download/AxCrypt-2.exe or download the program itself and attach it to whatever you send to the recipient.

That’s essentially what ‘self-decrypting’ archives are, except that we then append the encrypted file to the stand-alone. We don’t support that just yet, because there are simply so many things that are bad with the concept.

Oh, I just wrote blog post expanding on this subject, see http://www.axcrypt.net/blog/avoid-self-decrypting-files/ .

• This reply was modified 8 years, 3 months ago by  Svante.

[SvanteSpectator]

Hello,

First of all – you’re using the previous version of AxCrypt, which is not actively maintained. That being said, it’s not likely to be a problem with AxCrypt, nor is it likely to be resolved by upgrading to version 2.

As the message says, Access is Denied. This typically means that you do not have the permissions to either read or write to the file in question or to the temporary folder. Check that you can create files and folders in the document directory and %TEMP%\AxCrypt .

[SvanteSpectator]

Hello Cee,

Can you give a specific example? Normally, if a request is actually blocked, AxCrypt should go into offline mode and not even try to access the Internet, and thus not be delayed by timeouts or whatever.

Svante

[SvanteSpectator]

Hello Yehuda,

You’re right. Follow the issue here: https://bitbucket.org/axantum/axcrypt-net/issues/141/the-check-for-updates-button-only-works .

Thank you!

[SvanteSpectator]

Ok, Mr. Verhallen, I understand.

In the case of AxCrypt 2, the technical details are a little complicated, but essentially we’re using a “Sign In” metaphor for the operation that might be labelled: “Please enter the password to use for decryption and encryption during this session. We’ll use cryptographically strong mechanisms to also verify that this is indeed the same password that you used the last time you set or changed the password, in order to avoid  mistakes“.

The point being, that with AxCrypt 1 we had quite a few support issues where users would enter the password, twice, and mistype it both times. The next time, they did not, and thus could not open their documents. That was bad. We want to minimize the risk of that even further.

Also, by making you enter it just once at the start, the subsequent operations are very easy. No need to enter it each time you want to encrypt or decrypt.

We get more questions about the fact that you *only* have to enter the password once… See http://www.axcrypt.net/blog/leaving-computer-axcrypt/ .

PS

The GPL licensing has no bearing on sign in requirements or not. It’s a license I am granting “you”, it does not restrict what I can do or how the software behaves. No part of the code is licensed to us under GPL, it’s either written by us, in the public domain, or licensed under less restrictive licenses (Bouncy Castle and Json.NET are both licensed under variations of the MIT license, and as such are deemed compatible but less restrictive).

[SvanteSpectator]

Thank you Laurel,

It’s input from users as yourself that will ensure that AxCrypt 2 really will shine and succeed in the long run.

Please  report if you find that the light bulb does not light up as expected!

Svante

[SvanteSpectator]

Mr. Verhallen,

Can you please attach a screen shot of the screen where you get stuck?

There is no requirement to register every time AxCrypt is used. You do need to “sign in”, i.e. enter your password.

[SvanteSpectator]

Hello Laurel,

It is indeed intended to warn about such situations, an update being available being one of them.

However, it’s also made so that it does not do the update check too frequently, so it may take up to 24 hours after a new release until the icon changes color.

Is your green despite an update being available for longer than 24 hours, and you’ve had Internet?

Svante

[Author]

Posts