[AxCrypt SupportModerator]

Hello David,

Do you by any chance use the Secured Folders feature on the USB drive? That will keep the drive locked.

In the meantime we’ve created and assigned an issue for this. You can follow progress here: https://bitbucket.org/axantum/axcrypt-net/issues/417/axcrypt-locks-usb-drive .

Thank you for reporting this!

[AxCrypt SupportModerator]

Hello CUTR,

This is most likely caused by you requesting a password *reset* on June 4. You can’t reset the password to gain access to previously encrypted files, that’s not how encryption works.

The password reset function will let you sign in again to your account, using the new password. But, to open previously opened files, you need to know the original password.

That is why it’s asking for the “file” password, which here means the “password the file was encrypted with”.

[AxCrypt SupportModerator]

Hello john,

Thanks, but unfortunately that didn’t help at all. I was thinking if you had a “registry error”, you did something to fix it. But if you did get a message about an invalid signature, that either sounds like AxCrypt 1.x, or something completely different.

Anyway, happy it works for you.

[AxCrypt SupportModerator]

Hello Anonymous,

Yes, I am the lead developer. Really ;-) No, sorry, I won’t give you any more solid than that about this feature. Wish I could, but I’ve given up trying to predict the future since many years in the IT business with failed such predictions.

We’re not a large company, and we don’t have scheduled releases and our priorities keep shifting all the time since we try to be very flexible.

“We might”, “I don’t like adding options” etc reflect the fact that we also discuss these things internally, we let suggestions take a little while to settle before we rush off and implement, and also we have several definitely higher priority things to do first which in turn I can’t give any solid delivery dates on – so that’s why I’m responding as I am.

[AxCrypt SupportModerator]

Hello,

This would indicate that the copy on the PC where it did not work indeed is corrupt. If you wish, I’d be happy to check this. You can send the encrypted files (without the password of course) to our support email and reference me.

 

[AxCrypt SupportModerator]

Hello Mike,

This would seem to indicate that the file has been corrupted. How was the file stored, i.e. on what type of medium?

[AxCrypt SupportModerator]

Hello Mike,

Can you give more details about the origin of the file, and the version of AxCrypt used for encryption and also if different, for decryption?

[AxCrypt SupportModerator]

Hi,

A couple of weeks I think, but I won’t promise… ;-)

[AxCrypt SupportModerator]

Hello,

Fingerprint discussion aside, this is really about how should AxCrypt handle the situation of screen saver going active, going to sleep etc.

Unfortunately, there are two schools of thought among users:

1) Those who are very annoyed because they are not prompted for the password often enough. It is insecure they say!
2) Those who are very annoyed because they are prompted for the password too often. It is unusable they say!

We’ve tried to hit a balance here, but we’ll probably be adding yet another option (I really don’t like all these options…) to control the sign out behavior when the screen saver goes active. Maybe we’ll connect it to the inactivity option we already have. If it’s set to never timeout, we don’t sign out at sleep either. Or we’ll just have it as yet another option.

[AxCrypt SupportModerator]

Hello john,

Just what registry error would that be? For future reference…

[AxCrypt SupportModerator]

Hello Tom,

Thanks for the report. The Brute Force software is built and deployed without manual regression testing, we’ve updated tooling and dependencies but missed that.

Please try again and download an updated version 2.1.421 (or better).

Svante

[AxCrypt SupportModerator]

Hello Samuel,

No, you’ve understood it correctly. We always open in the default associated application. We don’t have a ‘transitive’ Open With option yet.

We try to keep it simple, and actually – try as I might, I don’t think I’ve had this request mentioned before… 20+ millions users and about 17+ years… It seems most settle on having one preferred application for a given extension.

I do understand why you’d want to be able to switch, but it’s not a common request apparently. Sorry, it’s not likely to be a priority in the near future.

[AxCrypt SupportModerator]

Hello Thomy,

Nobody should ever share a private key regardless of the software or specific use. That’s why the key is called private.

In order to open a Word file, you need Microsoft Word or compatible software installed.

In order to open a PDF file, you need Reader or compatible software installed.

In order to open a TurboTax file, you need TurboTax or a compatible software installed.

In order to open an AxCrypt-encrypted file, you need AxCrypt or compatible software installed.

So, in order to share an AxCrypt-encrypted file the other user must use AxCrypt (or compatible, but none is available as far as I know).

What you also do as a Premium user is to use the key sharing functionality (this is not the private key, it’s a different key – often called a session key) of AxCrypt by entering the other users email address to share with as recipient. Once that is done, you can send the file to the recipient who also needs to install AxCrypt (but does not need to be a Premium user). All this is explained and shown in videos and other material available at https://forum.axcrypt.net/ .

[AxCrypt SupportModerator]

Hello john,

Can you send a screen shot of how it looks like when you try to open the file (yes, I hear you’re saying nothing happens, but we’d like to see what it looks like before)?

[AxCrypt SupportModerator]

Hello Derek,

If you want to keep the encrypted file, make a copy and then select ‘Decrypt’ from the right-click menu in Windows Explorer, or select Decrypt from within AxCrypt.

If you want to stop encrypting the file permanently, just don’t make a copy first.

[Author]

Posts