January 13, 2017 at 14:17 #5198
(This post has been edited by a moderator due to irrelevant personal references)
- Who will benefit from “the ‘unlock each time’ security feature”?
- Give me an example of why somebody wouldn’t or “cant for some reason use a screen saver password”
- If the answer is that it’s not their computer then AxCrypt won’t provide any protection anyway.
- What the benefit of the ‘unlock each time’ feature would be for users who “savvy enough to understand the limitations and extent”?
- If somebody truly understands the limitations and extent they’ll realise that requiring ‘unlock each time’ will not give them any extra security.
- Why is a “screen saver with password alone is not sufficient to prevent somebody with physical access to your hard drive from operating on or taking the data on your drive.”
- How could you bypass the screensaver without AxCrypt destroying your encryption keys from memory? Restarting your computer (which is the only way to bypass the Windows lock screen or screensaver on any version of Windows) will result in the password being required by AxCrypt.
- The security measures “above are not activated by default in a number of operating systems”.
- So what? AxCrypt has built-in protection against this. Once the screensaver is deactivated AxCrypt will require the password. You don’t need full disk encryption, device locking etc. to benefit from AxCrypt’s protection.
- How can “someone with physical access to their drives can potentially operate on their data” considering the protections AxCrypt put in place?
(Edited) Please give a credible scenario and examples of how it can be bypassed.
(Edited) Referring to Svante’s article previously quoted, what parts are debatable?
January 13, 2017 at 15:01 #5201
- This reply was modified 5 years, 7 months ago by Svante. Reason: Irrelevant personal references
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 email@example.com . Just refer to me, and it’ll get to me. Don’t post meta discussions about this discussion here.January 26, 2017 at 00:16 #5298
I do not want to be repetitive but I would like the auto sign out feature back. I read through all the reasons here and I still feel that this features is important. I feel safer when I know that if for some reason someone is using my computer (sometimes I want to borrow it for a presentation, etc.) they can not have access to my information.
So add me to the people that is requesting this featureJanuary 26, 2017 at 12:36 #5308
Thank you for your input. It’s on the to-do list.February 8, 2017 at 20:52 #5451
Dale, I did not see this before now, but it looks a little dangerous… Looks like it’ll kill AxCrypt. Since you refer to ‘autohotkey’ of which I know nothing, but from the name it seems it could send keystrokes. Can’t you write a similar script that just signs the user out instead of killing the process?June 21, 2017 at 01:13 #7050
Hey everyone, I just installed version 2 of AxCrypt on my desktop (as part of getting the mobile version) and like the others here, am VERY disappointed that it no longer requires a password to view or decrypt each file individually. Having found this thread and read all the posts, I completely agree with Peter, Dale and Roque. Any use of encryption is better than none, and if we wish to use this product in the manner implemented so beautifully in version 1, we should have that option. I really hope you can add that feature soon, since I’m positive we’re not the only four on this planet who feel this way. Thanks!June 21, 2017 at 08:49 #7051
Thanks for your input. No, you’re not the only ones with this view. On the other hand we have also quite a few who initially say this, but then come back after a little time and say they now realize how much better the AxCrypt 2 way is ;-)
Please read this also https://forum.axcrypt.net/blog/leaving-computer-axcrypt/ before forming your final opinion.
That being said, we’re working on it…November 3, 2018 at 17:57 #11908
Have been using version 1 and just moved up to 2; also very disappointed with the lack of support for multiple passwords… and lack of support for requiring a password every time a file is opened.
My household has multiple family members, each with their own computer; own passwords. Axcrypt 2 works for that; however, everybody’s files are backed up to a shared drive, and replicated to one shared computer… thus we have multiple passwords on that shared computer.
The shared computer is locked in my house… for convenience, I’d rather not have it screen lock. Perhaps it is unusual, but I trust my family. It would be great if any family member is using the shared computer, they would just be prompted for their password when opening their file… but more importantly, prompted to set a password when they create a new encrypted file… so when it is replicated to their individual computer, it is encrypted with their password, not the password of the last family member to log into axcrypt. Yes, I could have multiple accounts on the shared computer (and actually do), but it is far more convenient to not have to logout/login every time someone wants to use it.
For the shared computer in my house; I’m generally not concerned about security… unless someone breaks into my house and steals it… in which case I’d really prefer that they had to enter a password to unlock the files. Seems unlikely someone would break into my house just to install a key logger on my shared computer; could happen, but a risk I’m willing to live with for the convenience of having an easily accessible shared computer.
Security is all about understanding and accessing risk. I’d like axcrypt to support my acceptable level of risk. Seems others would too. I don’t mind if AxCrypt defaults to very secure behavior, and even makes me read a warning to change that… but I’d still like the option, the option to select my own level of risk.November 5, 2018 at 19:59 #11932
Thank you for the detailed well-reasoned description of your use case.
Unfortunately, we just won’t support that use case. The reason is that for the situation you describe, using AxCrypt or any kind of encryption is just simply massive overkill – and may also lull some users into feeling secure. But they are not.
I fully understand the reasoning between having the option to disable some features or configure for your own perceived level of security. Perhaps you are in fact fully informed and this is just what you want and need. Problem is that it’s very unusual.
We have experience from millions of users of AxCrypt in both version 1 and 2, and we are very sure that enabling your use case, will cause many to believe it’s a better situation than it is.
At the very least, we recommend that separate users have separate accounts on the computer – they don’t have to have strong passwords (or even any passsword!). This is both more convenient – each user gets their own bookmarks, recently used items in Windows etc etc. And AxCrypt gets a chance to invalidate the current sign in session at the appropriate time.September 15, 2021 at 16:09 #22892
I am perfectly fine with the way password requirements are set in V2.1, but I have a small problem.
I have set the Inactivity Sign Out to 5 minutes, but in point of fact it never signs out – even after more than one hour.
Is something wrong with your program or am I doing something wrong.
By the way, I did test Logo+L to lock the computer and indeed when I reopen AxCrypt it is signed out.
I like that very much.
Jimmy MayerSeptember 17, 2021 at 08:00 #22916
Hello Jimmy Mayer,
We are tried to re-recreate the issue with our local environment, But not able to re-create the same.
Please more detailed(step by step)information about the issue and screenshot. We try to fix the problem.
If you have any queries, please feel free to contact our support via firstname.lastname@example.org.September 27, 2021 at 08:52 #23075
Error during startup – already cleared cache.
Uninstalled and reinstalled Axcrypt. Also the portable version is not working
‘The process cannot access the file because it is being used by another process
Windows version : 21H1 (19043.1237) Enterprise
———– Exception at 2021-09-27 06:44:31Z ———–
System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:53414
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at AxCrypt.Mono.HttpRequestClient.DoRequestInternal(String method, String content, WebRequest request)
at AxCrypt.Mono.HttpRequestClient.Dispatch(CommandServiceEventArgs command)September 27, 2021 at 12:08 #23080
Hello Bart Goossens,
Please avoid sending a same query in different mediums. You may get duplicate response.
Please send the complete error report to troubleshoot the issue. Please follow the detailed instructions to take the complete error report: https://www.axcrypt.net/blog/how-to-send-a-complete-error-report. Also, write a mail to email@example.com