Forum Replies Created
-
AuthorPosts
-
Hello Klaus,
From your problem description, it sounds like you’re using AxCrypt 1.x. Please enclose a screen shot to help us understand the issue.
You should also be aware that version 1 of AxCrypt is no longer actively maintained, so it’s very unlikely that even if there is a bug that we’ll fix it.
If you have not done so already, please check out the current version at http://www.axcrypt.net/ .
Hello James,
Not entirely sure what you mean. Unfortunately iOS 9 broke the old app, and it was also pulled from the store by the third party that made it (with our help and blessing, but still).
Right now we don’t have anything for iOS. We’ll be starting the final development of the iOS/Android app in mid-September.
Hello Imran,
It appears as you in fact have forgotten your password, since it’s the same password when signing in to https://account.axcrypt.net/ and AxCrypt 2 (when it’s online).
Please read the FAQ concerning lost passwords.
Hello Paulo,
No, you can do encrypt with the Free version, but it’ll use AES-128 instead of AES-256, and you cannot add recipients via the key sharing feature.
(Note to all reading this: Please do not add your question to an existing thread! Create a new one, even if your question is related to the question in this or some other thread).
Hello Paulo,
Yes, you always need a password to open an encrypted file, however AxCrypt does remember the password while you’re still signed in.
In order to share encrypted documents with others, you need the Premium subscription. But any files encrypted with Premium can be opened with AxCrypt Free (if you know the password).
Hello Jim,
In general, the “Shred and Delete” option should not be treated as a full data sanitizing operation. It’s very, very hard with modern hard disks (even mechanical) and SSD is particular to ensure that you’re really overwriting.
That’s why for example real-world intelligence service “Shred and Delete” is done like this: https://www.theguardian.com/uk-news/2014/jan/31/footage-released-guardian-editors-snowden-hard-drives-gchq instead of using sanitizing software of any kind.
The AxCrypt Shred and Delete options asks the file system via the operating system to overwrite the data as explicitly as possible, that’s it. There are no provisions for layers between saving copies, or in the case of SSD’s actually writing somewhere else due to wear levelling algorithms etc.
In actual use it works well enough to stop normal recovery operations and software to work in most situations, but armed with low-level forensics firmware and such, some or all information depending on the situation can probably be recovered.
Our suggestion is to use hard disk encryption (BitLocker and/or EFS) together with AxCrypt to beef up the security of the local PC, and to protect in case of the actual hard drive going AWOL.
Hello Alastair,
You’re right. We should update the documentation section with a more detailed feature-by-feature description.
Anyway, AxCrypt works by taking the original file, encrypting it and then deleting the original. When you double-click an AxCrypt-encrypted file, what happens is:
- The file is decrypted to a temporary location
- Windows is asked to open whatever application is associated with the decrypted file, i.e. Word for example.
- AxCrypt tries to determine if it can when the application that was started is done with the file. If it can, it will then wait for this and when the application is done, it’ll take the temporarily decrypted file and re-encrypt it back to the original location.
Sometimes, AxCrypt cannot determine when the application has finished as described in step 3. In the case, AxCrypt needs to be told when it’s ok to re-encrypt it back and delete the temporarily decrypted copy.
This is what the ‘Clean Open Files’ button does. You’re telling AxCrypt that now it’s ok to remove any temporarily decrypted files.
As for the link to “More on Local PC…” – it’s not a link, it’s a CSS/script thing which expands the text. You may need to have script enabled for it to work. If script is enabled, what browser are you using?
August 26, 2016 at 15:08 in reply to: Что делать если забыл пароль от зашифрованного файла???? #3969Hello,
Please read the FAQ at http://www.axcrypt.net/support/faq/ .
Hello Liz,
Can you please send an e-mail to:
support att axcrypt dott net
(replace ‘att’ with @ and ‘dott’ with . and remove spaces).
We need your email address in order to check your account.
Thanks for the report. Noted, until next time it happens…
Hello Robin,
Ok, glad to hear it.
You exit AxCrypt by using the ‘File | Exit’ menu. Clicking the Window Close red cross icon at the top right or ALT+F4 will minimize it to the tray.
Hello andrew,
As a final troubleshooting task, you might want to try and delete %localappdata%\AxCrypt – that’s the folder with all the AxCrypt settings, and then repair or re-install AxCrypt and finally try to start it with the –offline switch.
If you’re getting the same problem, something is broken in your system that is not related to AxCrypt I think.
Just type: %ProgramFiles%\AxCrypt\AxCrypt\AxCrypt.exe –offline into the ‘run’ command line.
You can also open a command window, and type ‘cd %ProgramFiles%\AxCrypt\AxCrypt’ and then ‘AxCrypt.exe –offline’ (in both cases without the quotes).
Hello Gerald,
We originally implemented Secure Folders like that. Unfortunately, there’s no way for AxCrypt to know ‘who’ or ‘why’ a file is created in the secured folder, and this caused serious problems.
A simple exampe:
You start Word, type some text, save your document in a ‘Secure Folder’. Boom – it get’s encrypted automatically. Word is now very confused, but it’s perception is that the file it just saved, just got deleted. Which it did. But it doesn’t have a clue that it’s now in AxCrypt-encrypted format.
Many similar situations caused us to abandon the automatic encryption, and instead have the ‘clean up’ broom so *you* decide when it’s time to encrypt the new files.
While we’re not there yet, plans include a really good command line AxCrypt that could be used for scenarios like yours, but for now, sorry – we don’t support it fully.
Hello vjon,
This is a frequently asked for feature, that we have deliberately not implemented yet. It’s not hard technically, but it has historically caused some major problems for users not realizing the full consequences (i.e. Encrypt c:\ recursive – yay, let’s encrypt everything, that must be secure!).
We’ve had product planning meetings and discussions about how to ensure simple operation for most users, without exposing lots of options, while still enabling such functionality for users who are qualified to use them properly. We’re getting to a point where we have a concept we think will work, so it’s now on the list.
https://bitbucket.org/axantum/axcrypt-net/issues/191/add-option-for-recursive-operation
-
AuthorPosts
