Forum Replies Created
-
AuthorPosts
-
Andrew,
No problem! Good luck.
Hello Dave,
If the file is encrypted, it’s encrypted and requires a password. You enter the password when you sign in to AxCrypt, and it stays signed in until you sign out, or it signs out automatically.
See http://www.axcrypt.net/blog/leaving-computer-axcrypt/ for a discussion around this.
John,
Yes, I agree that if you need it for 10 persons it is more significant, although I do mean €2 at yearly rates. €24/year + VAT (not sure if you are VAT registred or not).
On the other hand, stay tuned, we have already discussed gratis Premium for registred charities, possibly eductional institutions etc. Right now, the problem is we don’t have any way to manage such things. It will likely be a part of the functionality of our upcoming business volume discount management, so then we may well decide to offer it for free to charities etc.
The password protection of Word and Excel is useful, but less strong than the Free version of AxCrypt. Still, it may well be sufficient for your needs, and for those documents it’s probably in many ways easier to use. I would not store for example medical information or other persons financial situation in a password protected Word-document, but certainly things of lesser importance.
Andrew,
First – please don’t ‘hijack’ threads with one subject, with a post on another subject. Just start a new thread instead!
Anyway, the problem with ‘Save As’ and AxCrypt is that a file opened by AxCrypt is temporarily decrypted to a temporary location under %localappdata%\AxCrypt . That’s where the default ‘Save As’ location is.
While I do believe we can set the working directory to the original location, I’m not sure all applications will honor it. We’ll investigate and see how it works though. Follow the issue here: https://bitbucket.org/axantum/axcrypt-net/issues/139/set-working-directory-to-original .
Herman,
AxCrypt 1 had “remember this passphrase for decryption” as an option, while AxCrypt 2 always does this via the sign in mechanism.
What this means is that it’s working as designed. Once you are signed in, documents and files should open without asking for a password, until signed out. You can sign out from the menu, and you’ll also be signed out automatically when the computer goes to sleep or the screen saver goes active.
John,
What can I say? We need to pay the rent too, as you say, that’s life! Sorry, but we do need the revenue! Still, €2/month is not really that significant a cost, is it? That’s what we hope most people will feel anyway, compared to the benefits.
Good luck!
Hello Marty!
Small misunderstanding here maybe. AxCrypt uses your e-mail address as the name of your AxCrypt ID account, just like many, many services. This does not mean that you should actually sign in with your hotmail password though.
If you are in the process of setting a new password for your AxCrypt ID, it may be that our requirements are stricter than hotmail. Please hover your mouse over the error indicator to see the actual message.
If you are still having problems, please send a screen shot to: support at axcrypt dot net .
The idea is that to *share* a file key with someone requires Premium. To be shared with does not, and updating the file will work for the sharee as well. To *share* a new file, or add/remove a sharee, requires Premium.
June 23, 2016 at 08:02 in reply to: Option for enabling passcode when decrypting files w/ Axcrypt 2.x #3603Hello Keith,
I wrote a little longer text on this subject on our blog: http://www.axcrypt.net/blog/leaving-computer-axcrypt/ .
The short and long of it is that requiring password entry each time is not likely to increase the net security, on the contrary especially if it leads you to think that it’s safe to leave your computer physically accessible for anyone to use without requiring a Windows password.
Hello A,
No worries. Of course we won’t lock you out of your data because the Premium trial expires. The Free version will still decrypt and open AES-256-encrypted files, it just won’t encrypt with AES-256 but AES-128 instead.
Svante
Hi Sputnik,
I should have been clearer. When I wrote “…you think/want…” I did not mean you Sputnik, I meant someone else, any/many/all AxCrypt users. What you called “they”. So, we are saying the same thing here.
The shared password feature would be free. Needs some thought, but it could be a good idea actually.
Thanks!
Thanks Sputnik,
We appreciate your input. And, I mostly agree that it’s not what I think, but what you think that mostly matters. Except when it comes to actual security. AxCrypt will never add features just because it makes some users feel secure, unless the feature actually does add some security or at least does not lead people to think it’s more secure than it is.
That’s why I brought up the AES-256 example – that’s there because a lot of users want it. Not because I want it.
I think you’re bringing up an important point too which is separate from the “encrypt to .exe” function. That’s sharing between users. Your text made me think that maybe I’ll add a function so users can add secondary, or “sharing” passwords to their files for that particular purpose.
I’ve added a proposal to our issue list with that feature. You can follow progress here: https://bitbucket.org/axantum/axcrypt-net/issues/131/add-sharing-password .
Hello Yehuda, we’ll still be investigating your issue. There was no need to uninstall, deleting the %localappdata%\AxCrypt folder would have sufficed.
Anyway, yes you’re right – AxCrypt 2 has the behavior you describe. The reason is that although AxCrypt 1 was sometimes ‘smarter’ – it also failed worse. AxCrypt 2 has complemented a simple detection mechanism, with the ‘clean up’ broom. Which should work, if you in fact have closed the application. Otherwise, it will not.
Hi Sputnik!
Actually, the motivation for removing the self-decrypting option was not connected to Free vs. Premium as such. I just didn’t (and still don’t) think that it has sufficient merit.
That it’s not just to re-introduce it does have some connection to Free vs. Premium in the sense that we’re still very resource-constrained, so there’s a natural limit to what can be done in a given amount of time. If I had limitless resources, I would probably just add it back, since it would then be easier to do so than to defend the (still in my mind correct) decision to not include it in the first place.
Another similar issue that went the other way is AES-128 vs. AES-256. For the vast majority of encryption users (not just AxCrypt) in the world, there’s absolutely no difference in achieved security. However, AES-256 is very much in demand, and it does not hurt (anymore – it used to due to performance reasons) so there it is!
June 22, 2016 at 13:11 in reply to: I can open a an encrypted excel file just by double clicking it #3589Hello Rob!
Glad we could help you out.
For the theft scenario, nothing really has changed security-wise between AxCrypt 1 and 2, since it’s unlikely (I h0pe) that someone would actually steal your computer with you being fully logged in to Windows. And, even in AxCrypt 1, there was a check box to remember the password and then it would stay remembered until you signed off, not just a screen saver went active or so. So in that situation, AxCrypt 2 is actually better than 1.
Svante
-
AuthorPosts
