Forum Replies Created
-
AuthorPosts
-
Hello Anonymous,
There are several reasons for the creation of the account, some are related to the ability to have business model for the Premium version, some are related to offering convenience and security for the users. I’ll be writing a blog post about this soon, stay posted!
Yes, you can right-click and encrypt/decrypt files in Windows Explorer and double-click to decrypt/open/semi-automatically re-encrypt files.
Yes, AxCrypt 2 will upgrade an AxCrypt 1 installation. No need to uninstall first. No harm done either.
Hello,
If you cannot decrypt version 1-encrypted files with version 2, you’re not entering the correct password. AxCrypt version 2 is fully backwards compatible with version 1.
Apart from additions and some changes in terminology and look and feel, AxCrypt 2 is equivalent to AxCrypt 1 – it can encrypt and decrypt files and makes it easy to work with encrypted files.
Hello Leor,
Looking at our logs, we’ve sent the verification code to two different emails yesterday without any error indication. This means that it’s kind of out of our hands unfortunately.
Most likely it’s been caught by your spam filters. Check your spam!
We do everything we can to avoid this happening, but many filters are overly aggressive. We’ve even known filters that will refuse to accept anything sent from any IP-address in Sweden.
Hello Tom,
How about reading “Getting Started” on our web site ;-) ? We also have some very short introductory videos. Check out https://forum.axcrypt.net/ .
I think your main issue is that you’re trying to select folders, not files. AxCrypt encrypts files, not folders (although of course we do encrypt all files in a folder should you wish to).
In Windows and most operating systems, a folder is the container that contains files. Only folders have sub-folders (there’s not really anything called sub-files like you are mentioning, so I’m assuming you mean sub-folders).
Hello Gcentral,
1) You can’t make AxCrypt ask every time, but you can set it to auto-sign-out with different intervals. The most often is after 5 minutes of inactivity.
2) Right now you can’t change the password while offline, the whole idea is to use our web server infrastructure to ensure that a password change is synchronized across devices. It gets really complicated to keep track of the situation if let’s say you have 3 devices, and change the password on all three offline, to different passwords and also do it online for example. There’s no way we can handle a situation like that in a way a regular user will understand. It’ll just be too confusing.
3) We don’t support different online and file passwords as such. Once again, it gets too complicated for the majority of users, and for us to implement.
4) AxCrypt 2.x is backwards compatible with files encrypted with AxCrypt beta 0.9 in the year 2000 and every version since then – we have every intention to keep AxCrypt 7.x or whatever backwards compatible in the same way. As an extra precaution, we also recommend that you download the AxCrypt stand-alone version and store it next to your archive copies. If nothing else, it probably simplifies for you when you need those files. That of course depends on Microsofts willingness to be backwards compatible – but they have a pretty good track record there too. AxCrypt 0.9 mentioned above I’m pretty sure will run on Windows 10 (I have not tried, but I see no reason why it wouldn’t work).
Hello Anonynous,
I’m sorry, but it’s not clear what the question is that you are asking. Can you please elaborate?
Hello Dirk,
Depending on the app, the temporaries are cleaned when you close the document or when you fully exit the app. With exiting the app we mean really exiting the app completely – not just closing the document in this case. Notably Microsoft Office programs behave in this way. There may also be some issues with some Windows 10 store apps that do not exit even when you request them too, for example the image previewer does this sometimes.
If you are still having problems, please contact our support and include a screen shot of the AxCrypt main window when you have left-over files, as well as the files mentioned in step 2 here: https://forum.axcrypt.net/blog/send-complete-error-report/ . (We do not at this point need the event log mentioned in step 3).
Hello Dirk,
The location is for the temporary decrypted copies of the files. They will either be cleaned automatically at the earliest opportunity, or when you click the red clean “broom” icon in AxCrypt.
AxCrypt works by decrypting files temporarily and then launching the appropriate application for the decrypted file, which thus is entirely unaware of AxCrypt. AxCrypt monitors the system for the launched app to exit, and when it detects this it will re-encrypt the file and wipe (overwrite) the decrypted file and then delete it.
The public key is, well… public. So it’s no secret. It, and other configuration information is stored in some files in that location as well. None of the other information stored there is secret or sensitive in the sense that all that is in those files is apparent in the local system anyway, such as paths to recently used encrypted files. That information is used to populate the recent files list for example, and to keep track of files in need of re-encryption.
So, if you just let AxCrypt “do it’s thing”, the files you are seeing will be cleaned up when you’re done with them. Of course, do ensure you’re using the latest version of AxCrypt. We’re continually improving it, which includes optimizing such things as re-encryption.
Hello Hugh,
From the look of it, it’s “Bundle condition evaluated to false: NOT AxCryptLegacyInstalled” causing the problem. This in turn is probably the result of an attempted manual removal of the version 1.x of AxCrypt.
The check looks for the existence of the following registry entry: HKLM\SOFTWARE\Axon Data\AxCrypt REG_SZ Install_Dir . If you delete that, you’ll pass that test in the new installer.
However, you really should ensure that you uninstall version 1.x using the provided uninstaller… You might want to download the lastest 1.7 build, install and uninstall just to make sure that it’s done right.
December 16, 2017 at 14:56 in reply to: Windows does not reflect date of changes made to files encrypted w/ AxCrypt #8615Hello Jay,
The file in question is %localappdata%\AxCrypt\ReportSnapshot.txt . Note that %localappdata% is expanded by Windows to a directory specific for your installation. Typically something like C:\Users\[Your User Name]\AppData\Local .
Hello Craig,
Well, you can sign up on-line use a temporary password, purchase the license go offline and then *change* the password to something completely different. That way our servers will never see your ‘real’ password.
Hello Bob,
AxCrypt is a user mode client desktop application, and as such should work perfectly fine via remote desktop etc. It does nothing strange or advanced as far as the internal use of Widows API etc is concerned, so it’s very compatible.
From a compatibility point of view Premium is essentially identical to Business, so you can use the Premium trial month to evaluate fully in your specific environment. Contact support if you need to extend the trial period, we’re usually quite flexible with that (or just register a new account under a new email).
Hello Peter,
I’ve written a longer text on the fallacy of a multiple passwords strategy, you’re welcome to read it here: https://forum.axcrypt.net/blog/use-of-different-passwords/ .
It’s questionable if the Office password protection adds anything also, the problem being that Microsoft failed several times to implement it correctly, and now it’s often very hard to know just what version of the implementations is used in a specific situation. The most recent implementation appears to be “good”, but it’s often not used due to default settings for backwards compatibility etc. It’s complicated…
The idea with AxCrypt 2 is that you should use one single sufficiently strong password for all your needs. Also, we do provide a password manager, but I can of course understand concerns about that. However, stating “I’ve never been hacked, but LastPass has” is not really a valid argument. The most likely case is that on-one has tried hacking you, while thousands have tried hacking LastPass. The problem is that there is a big risk that the first one who tries to hack you succeeds, and you won’t know until it’s too late. In some ways, it’s actually a good idea to use a product or service which *has* been hacked, as long as the provider has acted correctly, and improved the product since. Then at least you know that someone has tried, found a problem, which subsequently has been fixed. That’s one known problem gone.
Hi Gene,
Literally anything? Even the menu or sign out?
Hi Gene,
Yes, that is the latest beta version. At what stage does it hang? What version of Android are you running in your device?
-
AuthorPosts
