Forum Replies Created
-
AuthorPosts
-
Hello Jeff,
Just right-click them in Windows Explorer or in the main window list of recent files in AxCrypt, and select the option to decrypt them.
Hi Ryan,
We usually work with different “themes” of development. So, for example, for one period we did the mobile apps, then the Mac desktop. Currently, we’re focusing on business administration functionality mostly – so right now adding the command line and SDK is not top priority. As for preference settings, we’re really trying to keep that to a minimum…
Hello sergio,
It’s unclear if you are making a statement or asking a question. In either case, I personally do not know what you mean with “the motorola radio” or how it can apply to AxCrypt. Please elaborate!
Hello Peter,
It is hard to make super-simple software that also caters to every use case. We try to make it as simple as possible for as many use-cases as possible. We do maintain that the key sharing functionality is so much better than the shared passwords used with AxCrypt 1.
You can always turn of the “auto-upgrade” of old files, so you can maintain them unchanged in AxCrypt 1 format and with the old passwords.
Nobody with access to your computer can read any encrypted files as such, however, anyone with access to your computer with your user rights and permissions can install any software on it so if you allow that you are insecure by default, regardless of AxCrypt-version or other software used.
Hello Nick,
If the password is something else than a word, essentially 8 more or less random letters and digits it will probably stand up agains most private attackers, but probably not against an attacker with a national budget such as a security agency or federal police if they are *really* determined.
AxCrypt 2 does ensure you don’t have too easy passwords, but of course it’s not fool proof, it can be “tricked” as well.
Hello Nick,
Since really changing the password is the same as changing the encryption, which means changing the encrypted files that operation must by definition be done on the files themselves. It can’t be done remotely.
If the password is weak, then it may indeed be possible to brute-force (i.e. guess) the password. It all depends on how weak the password is and how determined the attacker is.
When you use AxCrypt 2, it is actually quite hard to set a really weak password, since we require a minimum strength. For AxCrypt 1, no such check is made so there you can have the password “1” for example, or “Password”, or “qwerty” etc. That’s highly unlikely with AxCrypt 2.
If you password is either shorter than or equal to 4 or 5 characters in length, or is on the list of the most common passwords used then it’s very likely that a reasonably determined or even highly curious attacker will be able to guess it.
Hello Sarah,
Sorry, I did not read carefully enough.
There is no maximum as such, although performance may suffer with many files and folders. We are working on improving that.
I am not quite sure why it’s not working for you. Do remember that we don’t encrypt the files as they appear in the folder, you’ll have to click the ‘Broom’ icon to clean. Perhaps you can try it out with just two or three folders with two or three files each just to understand and more clearly see what is happening / not happening?
Hello Sarah,
You need to enable the option “Include subfolders” in settings. Then it should work as you expect.
Hello Gonzalo,
When you successfully sign in with your online AxCrypt ID password (i.e. our server verifies that the password is correct), the necessary information is synchronized with your local PC.
If you subsequently do:
1) Change the online password via the web.
2) Prevent AxCrypt from accessing the server in one way or another.
3) Sign in to AxCrypt on your local PC, and provide the password originally used before you did 1) and 2), then you’ll get the above dialogue.
May 30, 2018 at 09:39 in reply to: Version conflicts: Attempt to open file with V2 corrupts file for V1 #10686Hello Julius,
There is no single “downgrade to version 1” command unfortunately.
What you can do is to decrypt them, and then re-encrypt them with version 1 – and change the setting in your version 2 to not automatically upgrade. Version 2 will work fine in version 1 format as well, but not the reverse as you have found out.
May 29, 2018 at 16:49 in reply to: Version conflicts: Attempt to open file with V2 corrupts file for V1 #10684Hello Julius,
It’s not a bug. When you open a version 1-file with AxCrypt version 2, it will be upgraded to version 2 format unless you disable this function. So the file is not corrupted, it’s just upgraded and thus not recognizable by version 1 software.
You can disable this automatic upgrade.
Hello Amaury,
Yes, http://www.axantum.com describes AxCrypt 1 which is no longer maintained.
There is currently no planned date for the command-line version. You can always roll your own by integrating with the source code (it’s actually not that complicated for a simple use-case). We do have other requests for this functionality so we will try to deliver something not too far in the future.
Hello Gonzalo,
There is no “local password” with AxCrypt 1.x in any meaningful sense. Each file encrypted with AxCrypt 1 is encrypted with the password used at the time. To ‘change’ it, you’ll have to decrypt it and re-encrypt it. AxCrypt 2 normally does this automatically when you open an AxCrypt 1 file. There is also a function in AxCrypt 1 to upgrade version 1 files to version 2, and at the same time of course re-encrypt them using your version 2 password. This is probably the function you are looking for.
Hello Amaury,
What I mean to say is that sometime in the future we’ll implement a separate command line utility for AxCrypt 2. At this time we do not have one. I am sorry.
Hello Amaury,
It looks like you are trying to use an AxCrypt 1.x command line with AxCrypt 2.x. AxCrypt 2 does not support the command line as yet (and never will quite like that, it’ll be a separate command line executable), and AxCrypt 1.x is no longer maintained although it is of course available still.
-
AuthorPosts