Open M0rpheusz opened 1 week ago
Revert ‘Disable insecure “SHA-1” hash’ because Battle.net uses this insecure hash. You can enable everything else in the section.
Thanks for the reply, I'll try it and get back to you if it worked or not.
We cannot fix battle.net client, they're simply not following basic security best-practices.
Any concrete way we can improve privacy.sexy?
https://github.com/undergroundwires/privacy.sexy/issues/181#issuecomment-2211749777 https://github.com/undergroundwires/privacy.sexy/issues/430#issuecomment-2383697938
Description
I have run the privacy.sexy script on the security level “ Strict ” but when I run it, everything works except that I can log in to my Battlenet.net account, I have already found a thread here where someone had a similar problem, unfortunately his solution does not work for me ( allow TLS 1.0 and TLS 1.1 ) What can I do now ?
Please help me !!!
How can the bug be recreated?
However, I created a backup beforehand and then restored it, so I can reproduce the error again if I want to.
Operating system
Windows 10 IoT Enterprise LTSC
Script file
privacy-script.zip
Screenshots
No response
Additional information
No response