search

HotCakeX / Harden-Windows-Security

Harden Windows Safely, Securely using Official Supported Microsoft methods and proper explanation | Always up-to-date and works with the latest build of Windows | Provides tools and Guides for Personal, Enterprise, Government and Military security levels | Read The Rationale https://github.com/HotCakeX/Harden-Windows-Security/blob/main/Rationale.md
https://hotcakex.github.io
MIT License
1.84k stars 143 forks source link

[BUG?] TLS Security - Break Battle.net Launcher #38

Closed Tumeez closed 1 year ago

Tumeez commented 1 year ago

I noticed that TLS Security breaks Battle.net Launcher.

Virtual Machine: VMWare Workstation Pro 17.0.2 // Win 11 Enterprise 22H2 fresh installed, including all updates up-to-date.

image

image

After I apply TLS Security part, the machine can't connect to Battle.net anymore. I test every combination, other parts are okay with Battle.net.

HotCakeX commented 1 year ago

Hi, Please take a look at this thread: https://github.com/HotCakeX/Harden-Windows-Security/discussions/28

Another user had the same problem. Battle.net requires an old cipher suite which is not very secure and the TLS category disables it, but nevertheless, you can enable it again by running this in an elevated PowerShell:

Enable-TlsCipherSuite -Name "TLS_RSA_WITH_AES_256_CBC_SHA"

Please let me know if that fixes your problem. If it does, I will temporarily move it from TLS category to TopSecurity category since it's causing inconvenience for users, when Battle.net stops using that cipher suite, then I'll return it back to the TLS category.

Tumeez commented 1 year ago

Hi, Please take a look at this thread: #28

Another user had the same problem. Battle.net requires an old cipher suite which is not very secure and the TLS category disables it, but nevertheless, you can enable it again by running this in an elevated PowerShell:

Enable-TlsCipherSuite -Name "TLS_RSA_WITH_AES_256_CBC_SHA"

Please let me know if that fixes your problem. If it does, I will temporarily move it from TLS category to TopSecurity category since it's causing inconvenience for users, when Battle.net stops using that cipher suite, then I'll return it back to the TLS category.

Test it with my virtual machine. Works very well. After that command, Battle.net launcher works like meant.

HotCakeX commented 1 year ago

Great thanks, updated the script with the change 🙂