Forum Replies Created
-
AuthorPosts
-
Hello Jair,
Please refer to the instructions at http://www.axcrypt.net/ . There are videos and text explaining how everything works.
If you have encrypted a file with a password, you need to know that password to decrypt the file. You can reset the password for the account, but this only gives account access – you still need to know the password used to encrypt the file.
Hello romy,
Key sharing is a paid feature – receiving key shared files is a free feature. So, to be able to encrypt and key share files seamlessly within your research group you’ll all need to have a paid subscription.
October 17, 2018 at 10:58 in reply to: AxCrypt asks for my Email address like if I was using it for first time. #11567Hello Eric,
It’s hard to say exactly, but typically this happens if you’ve cleaned out all files in the Windows temp folder for example, or used the built-in ‘Clear All Settings and Exit’ function of AxCrypt.
You may also have created a new user on your Windows computer or something similar.
There should be no problem entering your email, and if you are online it will see that you already have an AxCrypt ID and then you just enter your regular password like before and you’re up and running again.
Hello Jake,
This does not in any way sound like a direct AxCrypt problem. An AxCrypt-encrypted file is just that – a file. There’s nothing special or magic or anything about it. It’s just a file. It’s nothing I’ve heard about before – disappearing AxCrypt files.
Sounds like it’s hard for us to help you out here. Sorry…
Hello Bernard,
Sorry, but I do not understand what you mean when you differentiate between “password” and “crypt/decrypt key”. There’s always just the password – which is used to encrypt/decrypt.
So, when you say “_I do know the crypt key i used but not the password_” I don’t now quite what you mean.
If you have forgotten the password used to encrypt the original file, then you can’t decrypt. Please read the FAQ at https://forum.axcrypt.net/ .
Hello Bernard,
You can decrypt your AxCrypt 1-encrypted files with AxCrypt 2. Just sign in to AxCrypt 2, and select “decrypt”. If your AxCrypt 2 password is not the same one used to encrypt the file, you will be prompted for the original password.
Hello Chris,
Version 1.7 is deprecated. It is unmaintained. It is unsupported. You are free to use it, but discouraged to do so for the named reasons. It does not support 256-bit encryption.
As for the the multiple password requirement – you should not be using that either, especially if you are keen on real security which seems to be the case.
Please read my blog post about this, here: https://forum.axcrypt.net/blog/use-of-different-passwords/ . The gist of the article is that using different passwords for private files “at best it adds no security and at worst it causes a situation with *less* security“.
Hello Derek,
Great! I was probably going to suggest the nirsoft software as the next step – it’s very useful to understand why shell extensions are not working as expected. I have no idea either why they would be disabled, especially after a re-install.
Hello Derek,
If it used to work, and now doesn’t, something must have changed. You may want to try to uninstall, and re-install the distribution.
If that doesn’t work, some other shell extension may be the problem.
Hello Neeraj Goel,
You will have to remember the password – if that’s what AxCrypt says is the problem. Please remember that passwords are case and space-sensitive! I.e. “password” is different from “Password” and “a secret” is different from “asecret”.
Hello Will,
Just right click the file(s) and select AxCrypt | Decrypt, and they will be decrypted to their original form. You do not need Premium to do this.
Hello Monkey,
Thanks for the information. We’ll have to investigate and see if we can reproduce this. It is known that AxCrypt needs to be improved for large amounts of files and folders.
I’ve added your findings to the following issue: https://bitbucket.org/axantum/axcrypt-net/issues/315/performance-problems-with-10000-files-in .
Hello RS,
Thank you for your feedback!
I’d still like to reply with some facts.
A big problem with the old AxCrypt 1 was that the *encryption* password was not in any way verified. This opened for scenarios with many different encryption passwords, as well as typos. The current AxCrypt 2 design where we keep to one encryption password that has to be verified (in a cryptographically secure manner) has drastically reduced the number of incidents with users not being able to access encrypted data due to forgotten passwords or typos. That’s a fact.
If you use AxCrypt 2 from Windows Explorer, like AxCrypt 1, the normal workflow is identical. The looks of the dialogs are different, but this the same number of clicks and keyboard hits as when using the ‘remember this for encryption’ and ‘remember this for decryption’ in AxCrypt 1. That’s a fact.
You write that the use of the cached password feature is a security risk because “if anyone manages to get access to the computer and the user is signed into Axcrypt the person has access to encrypted files!“. That’s simply not true, unless of course you left the computer entirely logged on to Windows with AxCrypt open. If you do, you’re pretty much out of luck security-wise anyway. If you sign out, if the screen saver goes active, if the computer goes to sleep, AxCrypt will sign out. There’s also an option to set a timeout for AxCrypt, just like a screen saver.
And no, we don’t want to force people to log on to the AxCrypt site to track them. We don’t track logged on users. However, we do want to try to make AxCrypt survive and evolve. This requires money. Not even one in a ten-thousand donated even $10 for AxCrypt 1. I had two options – kill AxCrypt entirely, or try to find a compromise by still offering AxCrypt for free with basic features, and then add features to make it worth paying for. For payments to work, we do need some kind of account mechanism. However, the main function of the online account is to host the password manager, and the key pairs used for key sharing (sharing encrypted files without sharing passwords), and to serve as a way to validate the encryption passwords used (see above).
You are welcome to use AxCrypt 1 of course – but beware, there’s no support and no maintenance. It’s obsolete, sunsetted abandonware at this point. Use at your own risk.
Hello Mike,
Ok, yes, in that scenario it’s not a perfect match. The “obvious” way to handle it is to encrypt the files on the desktop, and then backup them in the normal way. If the videos are large, it may not be that convenient though. Problem here is of course that you’re not actually backing up the files, but a processed version. We don’t really support this scenario that well.
Another way to handle it, which might actually be beneficial, is to let AxCrypt handle the collisions, and thus save successive generations of the files. IIRC AxCrypt will handle collissions by generating successive unique file names for the encrypted files, so MyFile.txt will get encrypted as MyFile-txt.1.axx if there already is a MyFile-txt.axx, leaving both . Do try this out, I am not exactly sure from memory just how this is handled in the different scenarios.
Hello Monkey,
Yes, for subfolders to be included you should enable the ‘include subfolders’ option. The reason there’s a warning is simply because it’s easy to make mistakes and with this option enabled, the consequences are potentially so much greater.
Subfolders themselves may not be deleted if they contain for example hidden or system files which are excluded from deletion buy AxCrypt. Once again to protect from dangerous mistakes.
The secure delete function opens the file for write, and then writes a random sequence of bytes over the entire file, flushes everything to disk and the deletes the file.
-
AuthorPosts