Replies: 3 comments 2 replies
-
Hi, thank you very much, The issue with the battle.net client is mentioned on the readme on the TLS category, it also links to a discussion where i talked about it with someone else. Removing all protections wasn't really necessary but it's okay, you can apply them again any time. So before thinking about implementing a separate option for every single 250+ policy that is applied so far (which is a lot of work), let's talk about other problems you are facing so i can have the full picture. Because for the Battle.net client, i can add a check to the TLS category in the next version to detect Battle.net client on the system automatically and then keep the TLS cipher suite that it needs for connectivity, so user won't have to do anything extra. If you let me know about other problem(s) i can think about better solutions for them as well. Thanks |
Beta Was this translation helpful? Give feedback.
-
Hi. Thank you for the quick response. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Just released the version 0.6.8 that automatically detects BattleNet client on the system and uses the appropriate cipher suite for the TLS category that allows the client to connect to the servers. All you need to do is to run the same command again that you were using, which automatically updates to the latest version, and then run the TLS category. Or you can just use this command for even more automation :) Protect-WindowsSecurity -Categories TLSSecurity If you encounter any other problems please open separate issues for each of them so i can address them one by one asap. Thanks! Here is the release notes for the version 0.6.8: https://github.com/HotCakeX/Harden-Windows-Security/releases/tag/Hardening-Module-v.0.6.8 |
Beta Was this translation helpful? Give feedback.
-
Hello, @HotCakeX.
I want to thank you for the Harden Windows Security module. It is amazing and the best in what it proposes. Together with all the documentation.
I want to suggest the capability to enable and disable the items individually.
Why?
The latest and most serious problem I had was with the Battle.net desktop app (today).
I was not able to log in it. It could authenticate my login information, ask and confirm my 2FA. But after that, this error always appeared:
Nothing appeared in the Protection history of Windows Security.
I use the latest version of Windows.
I don't have any third-party security apps.
The problem did not happen in Windows Sandbox, using the same computer.
I painfully opted to use Unprotect, first only removing Process Mitigations, then, removing App Control Policies.
Those did not work, so I used Remove All Protections.
It worked. So, some item or items break the app.
Thank you very much for you attention.
Beta Was this translation helpful? Give feedback.
All reactions