Forum Replies Created
-
AuthorPosts
-
Minor update on this issue. Checking the .NET source it turns out that this error stems from Windows returning an error code WSAEPROVIDERFAILEDINIT on a call to WSAStartup().
This in turn can be caused by various issues in the system environment, most often according to a Google search on the issue:
– Insufficient permissions (non-standard settings to UAC or setting ‘Run as Administrator’ for the executable might cause this for example).
– Not having the system variable ‘SYSTEMROOT’ set. This should seldom be a problem for AxCrypt which runs in an interactive session most of the time. Of course if files have moved and SYSTEMROOT is no longer correct, this could also cause the problem. Apparently this is how the appropriate dll is located. Among other things, mswsock.dll must be found.
– Broken or partially broken TCP/IP stack in the system.The fix being implemented will just silently ignore this error, and the requested functionality lost unfortunately – until I get more information or can reproduce the issue locally.
Hello again B Scache,
We’ll investigate the –offline issue at the same time, it may be that we’re still trying to initialize something even if we don’t actually do any network calls.
Thank you for the information!
Hello B Scache and Andrew,
We’ve investigated the issue further, and it’s a very simple call that fails. Microsoft does not document any conditions under which it may fail like this. Since this statement is executed everytime AxCrypt is started (if not in always offline-mode), and we only have these 2 reports it’s surely something specific in your respective systems that is unusual. Not necessarily wrong, just unusual. Of course we should AxCrypt should handle this to, the point here is that it’s not a general problem.
It would be good to understand what circumstances lead to this, in order to fix it as well as we could, so I’ll persist in asking: Do you have any idea or suggestions about something which in any way is out of the ordinary as regards to the networking in your environment? VPN software, extra network cards or USB networks, some unusual configuration, anything?
In the meantime we’ve logged an issue for this, and if nothing else comes up so we can understand this issue, we’ll issue a bug-fix that simply does not use this feature if it is broken like this. It does mean that if this is the fix that will be made, that we’ll silently ignore the error and disable the functionality which is not vital, but sub-optimal. We’d rather understand it and work around it properly.
You can follow the issue here: https://bitbucket.org/axantum/axcrypt-net/issues/200/socketexception-the-requested-service .
Hello James,
Yes, you can of course downgrade to AxCrypt 1.7 and thus keep being compatible with the old iOS app. Please be aware that files encrypted with the new AxCrypt 2 software are not possible to open with AxCrypt 1 or the iOS app – so for these files if any you’ll have to decrypt and then re-encrypt with version 1.
I suggest you download the stand-alone version of AxCrypt 2 (it’s fully featured, just without the Windows Explorer integration) since it can co-exist with an installed version of AxCrypt 1.
The current plan is to release the iOS app later this year.
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.
-
AuthorPosts