Forum Replies Created
-
AuthorPosts
-
Chris,
Harry is entirely right. Thanks!
Hello Adam,
That’s strange. Windows sometimes displays that message, when we released a new version but we quickly get the reputation needed to avoid. Unfortunately Microsoft has chosen to respect the fact that we’re digitally signed with a proper certificate.
You should be able to run it anyway, under More Info. See here: http://www.howtogeek.com/123938/htg-explains-how-the-smartscreen-filter-works-in-windows-8/ . Do you have a screen shot of the “More Info” screen?
Also, ensure that you downloaded the most recent version of AxCrypt from https://forum.axcrypt.net/ and that the digital signature is correct by checking file properties after download, and select “Digital Signatures”.
Hello Cees!
Thanks for the feedback, it’s high on the prio list… You can monitor progress here: https://bitbucket.org/axantum/axcrypt-net/issues/191/add-option-for-recursive-operation .
Hello Claudio,
When you open an AxCrypt 1 file with AxCrypt 2, it gets re-encrypted with your new AxCrypt ID password, i.e. the password you set when you created the account.
If you previously shared these files with others, you should upgrade them all to the new AxCrypt 2 software – and then add these account emails to the list of recipient key shares.
AxCrypt 2 has a more sophisticated way to share encrypted files with other. You do not need to share any passwords any more, and every one uses their own one password to AxCrypt.
Instead of using different passwords for different sharing groups of persons, you add the email addresses of the persons you want to share the access to the file with using the key sharing feature.
Hello gregg,
Can you send a screenshot of the situation? It’s not entirely clear what’s not working as it should here.
AxCrypt has two tabs “Recent Files” and “Secured Folders”, maybe you mean “Recent Files” when you write “secured file”?
Thanks James, exactly so.
January 15, 2017 at 13:36 in reply to: How secure axcrypt deal with temporary file when decrypt a large encrypted file? #5219Hi Allen,
AxCrypt stores it’s temporary and working files in “%localappdata%\AxCrypt\” and folders below .
Hello Štefan,
There seems to be something broken… It’s supposed to download properly, as long as you actually use the the link from the axantum site. Direct links should behave as you describe. However, when I try it now, it seems that it’s not working as intended.
We’ll have to investigate. It’s supposed to work, but we have previous reports of it intermittently not working as expected.
January 14, 2017 at 21:48 in reply to: How secure axcrypt deal with temporary file when decrypt a large encrypted file? #5213Hi Allen & Abraham,
Temporary files are always wiped / shredded (i.e. overwritten with random data) before deletion. This is the same for both Free and Premium users.
Please note that modern SSD devices often have a feature called “wear levelling”, which causes such wiping to be less secure than it might seem. With the proper software, it’s often possible to recover data that logically is overwritten (but in actual physical fact is not). It’s not trivial, and it can’t be done with regular file recover tools. It needs special software that interacts directly with the SSD device, but the point is that it’s possible.
January 14, 2017 at 17:46 in reply to: Will I lose access to my files if my AxCrypt ID account is hacked? #5207Hi Gene,
No worries. Your account has not been hacked. You will not lose access to your files.
Someone, probably yourself, have registered your email address in our system. When this happens, we ask you to verify the email by clicking a link or entering a verification code.
No-one did this during the time period we’ll wait for this, and what this email says is just that – since you did not verify it, we’ll just remove you.
This has no affect to your ability to access your files, as long as you know the password used to encrypt them.
Annalisa,
The message is exactly the one you get when you have Lavasoft Web Companion installed. Please uninstall that, and AxCrypt should be working normally.
Sorry guys! I really like the discussion, but not the implied/expressed personal stuff, so I did some insenstive hacking to the posts removing and editing some parts.
I think your posts still contain the same information and opinions, just with focus on the subject matter.
I can’t keep doing this though, so if it keeps getting out of hand again, I’ll have to shut it down.
I’m trying to be impartial three ways here, but if you think I can handle this situation better – please drop me an email via support@axcrypt.net . Just refer to me, and it’ll get to me. Don’t post meta discussions about this discussion here.
Hello Annalisa,
A screenshot would indeed help a lot, but the most likely reason is described here: https://forum.axcrypt.net/support/faq/#lavasoft-crash .
Guys! Respect, please, or I’ll have to start moderate this. Please? Go for the issue, not the person.
The discussion is interesting, and I actually think all parties have something to learn here. But keep a nice tone, and stick to talking about the problem, not individual persons!
While the information is hard to really understand from Microsoft, here are are some facts about the term “device encryption”:
– It’s sometimes used as a generic term, i.e. “On Windows 8.1 Pro, device encryption can be done with BitLocker”.
– It’s sometimes used as a specific feature name, i.e. “Windows 8.1 RT includes Device Encryption (a stripped down version of BitLocker)”.
– BitLocker on desktop PC’s is not enabled by default. It can be in Enterprise environments for example.
– Device Encryption is enabled by default on certain devices, including mobile and desktop PC’s provided a number of critera are met, which includes a TPM that supports connected stand-by, it’s a clean install, the manufacturer has chosen not to disable it etc.
– Device Encryption, if supported and enabled, will not actually protect your data until you sign in with an online Microsoft Account or a domain account, with administrative privileges. Before then, the drives are encrypted, but the volume master key itself is not protected, making it available to anyone using the computer with a clear key. This is equivalent to BitLocker suspended state. After the administrative sign in, a recovery key is generated and uploaded to the Microsoft Account and the TPM is configured to not release the volume master key using the clear key. At this point, the drive is protected.
So, to sum up the findings on underlying hard drive encryption on Windows devices:
While many new tablets and PC’s will have it enabled and activated by default, it’s a good idea to check and verify since it’s so transparent you can’t really tell if it’s on or not unless you check.
It’s a good idea to ensure it is enabled, as it complements for example AxCrypt in many ways.
Thanks for providing incentive to write up this summary. It’s far from a clear-cut case, and available information is easy to misinterpret, to a large degree because of confusing naming practices by Microsoft.
Hello magic,
Whish we could have everything free for everyone… But the fact of the matter is that for AxCrypt to keep existing, we need revenue.
The previous iOS version is a good example of the problem. It was made as cooperative project with another developer. I provided the core code and they did the iOS part as an educational project for their staff. Great while it lasted.
Then the company said, “Thanks, that was fun, but we can’t and won’t maintain it.”. At that time it became abandonware, which was first removed from the App Store and then iOS 9 broke it compatibility-wise.
We want AxCrypt to be available on all relevant platforms, Windows, iOS, Android, OS X and hopefully Linux. Maybe it’s just me, but I just can’t do that by myself while at the same time having a day job to pay the rent and also have a life. I’ve not been able to find enough other volunteers.
As you say, the app is basic. In order to change that, we need to spend many hundreds, perhaps thousands, of hours to keep developing it.
That’s what the revenue is for. To develop AxCrypt. At this point every cent goes right back into the product. If you like, see the subscription fee as your contribution to the project, because that’s what it is.
The next step is bringing AxCrypt to the Mac, and we’ll be adding functions to the desktop version as well as the mobile apps.
-
AuthorPosts
