Forum Replies Created
-
AuthorPosts
-
Haha!
No, I would not expect that you or most people would deny me a few bucks for the Premium features if they found them useful. I was a bit ironic, and also am a full believer in full disclosure, and this is a public forum so that was more for the benefit of other readers who may pose the follow-up question – if the Premium status is stored locally, can I hack it?
Good luck!
Svante
Hello,
AxCrypt works fine in offline mode with no Internet or server access, except of course for the features which are server based. But plain encryption/decryption is of course fully offline functions. Currently you do need server access the first time you install AxCrypt on a new computer, but not thereafter. We’ll enable pure offline registration in the not too far distant future, if nothing else to ensure everyone that regardless of our servers or our business still operating you can always access your files, even after getting a new computer.
Premium status is checked and updated when online, and the state is cached until the next time. Is it possible to find how this is done and cheat? Sure. But do you really want to mess with and hack an encryption application, all in order to deny us hard working developers a few bucks so we can continue to support and develop this application?
Also, several of the Premium functions are server based (that’s one of the reasons it’s a subscription, not a license) and thus a local hack won’t help.
Hello Ken, and thank you for your insightful comments.
The simpler, offline, standalone version is definitely to be. Exactly how it’ll work is still to be decided, we’re considering various options.
Your escrow scenario with the split key operation, is something else again. Not really sure how I’d like that to work. Will have to think about that one some more. I still do not like the idea of going back to use of multiple passwords à la 1.x, I don’t think that’s the solution here.
I do have a thought about the possibility to *add* passwords to files, that would actually fit your bill. See https://bitbucket.org/axantum/axcrypt-net/issues/131/add-sharing-password . This would not have the risk we’ve seen of people forgetting what they entered, you’d still use your own password normally, but you could add a “sharing password” (and construct it like you suggest in split parts) and give to other people whole or in part.
Hello Mike,
Currently we support PayPal, and PayPal in turn support credit cards (without opening a PayPal account actually).
We’re planning another payment integration, but it’s not decided or developed yet.
Hello ChristianM,
As a final resort, the source code is available on third party servers, and there’s nothing on our servers that is really needed to decrypt any files as long as you know the original password used.
We’ll be implementing a simple way to achieve this soon as well in the main distribution, see https://bitbucket.org/axantum/axcrypt-net/issues/60/support-offline-registration-and-key-pair . The main challenge is how to make this both safe, and also not the standard since we’re seeing so many benefits in having real, verified email-addresses. For one thing, support is working much better!
Also, the key pair mentioned in the issue is a convenience, it’s not *required* in order to actually decrypt files.
Hello Barkeley,
We agree – mobile is our highest priority for the next development.
As for self-decrypting, there are just so many disadvantages. I really think that having a self-contained, stand-alone, fully-featured executable is much better, and fills the same function. We’ll be ensuring that it can run well without any server or internet access too, for that reason among many.
Hello Barkeley!
You are so right, lot’s of confusion. Even you still have some confusion. We were to be honest taken by surprise by how hard this obviously is. We’re continuously working with improving the software as points of pain become clearer, both how we write tips and texts, and how the program actually works.
AxCrypt was and is still a password based encryption software. In AxCrypt 2 we use the password for a little more things, but it’s still in the end, just that. A file encrypted with a password.
One part of the confusion is that we now require that password to be associated with a verified email address. This is for several reasons. This in turn causes more confusion, because that password is often not the same as the password used for old AxCrypt files, especially not if you have more than one password used for old files, then it can’t be the same as all of them of course.
Some points in your post that needs clarification:
You write: “If it is easy to reset your forgotten password account by the “I forgot” feature via e-mail, warning is needed about the fact you will not be able to open file with the old account password.”
There is a big red warning, but the warning is not about “not be able to open a file with the old password“. Depending on what you mean, that’s not the case either. A file that was encrypted using a given password is always encrypted with that password, and you can always open the file with that password. It can also be opened with the account password, *unless* you do a password *reset* on the account. Then it can’t be opened with the new account password (*unless* of course that new account password just happens to be the same that the file was originally encrypted with ;-).
You write: “To open 1.7 files I then need two passwords, first the account then the 1.7 file password.” No, you do not. Only the first time. AxCrypt will by default convert opened old 1.7 files into version 2 files, using the account password. There’s also a function to batch convert many files at once. Thereafter you’ll only need the account password, and only once per session.
You write: “I regret not to be able anymore to use short-easy-to-type password for some files and up-to-13 digits with mixture of signs for very sensitive datas.”
Please read http://www.axcrypt.net/blog/use-of-different-passwords/ for a longer explanation of why we do not support this scenario, and why we don’t think it’s a good idea to start with.
July 11, 2016 at 22:51 in reply to: Can't open existing Axcrypt files with latest version of Axcrypt #3742Hello Andy,
This thread is to say the least a bit confusing. Too many posting their own issue. Each thread should essentially be per one single user/issue.
Anyway, this means I’m not sure just what “Now I have done as you have suggested” means in this case.
We do not know of any confirmed case of files actually opening in version 1, and not in version 2. There was an issue in a previous version, where some files would not open after a password change, but that has been fixed.
The best way to make sure that it’s not a problem with the program, is to temporarily uninstall AxCrypt 2, re-install AxCrypt 1 and see if you actually can open them there. If you can’t – then it’s not a version problem. If you can – re-install version 2 again, and repeat.
Ok, thanks Peter. I’ll look into that asap. I know this works for other users, so there’s something fishy here. You’re signing in with the same AxCrypt ID? Our support for multiple users on the same machine is not quite there yet.
Hello Peter,
Thanks for the feedback. When you say ‘Sign out and in again’ – do you mean just AxCrypt, or do you sign out of Windows?
Svante
Matt, your screen shot did not make it, but as long as you’ve got it working. Still, it concerns me if there are problems with the source code downloads.
Hello Matt,
Just re-downloaded the zip using your link, and BERSequenceGenerator.cs is still there!
Do you not see it here after unzipping?
Hello Jamesmaher,
Not sure what we or AxCrypt can do about write protected external hard drives. I’m sure there’s some misunderstanding here. Perhaps you can explain in more detail, preferrably with scren shots?
July 9, 2016 at 21:25 in reply to: Security Problem : Axcrypt do not ask for password in offline mode #3729:-)
Svante
Hello Fran,
Not sure I understand fully.
1) Yes, the account password is essentially the same as the “old” passphrase.
2) The standalone version 2 works the same as the installed version 2, except for explorer integration. The files encrypted with version 2 are encrypted with the account password, and you need version 2 and that password to open them.
-
AuthorPosts
