-
-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
evil-winrm: fix OpenSSL 3 error #3620
Conversation
Fixing the issue linked in #3593 by enabling legacy protocols that Evil-WinRM uses for attacking the target machine. The issue is solved by enabling the legacy protocols after the pkg installation that have been kept disabled by default by OpenSSL maintainers with the latest OpenSSL version.
You could try adding |
I tried to install openssl-1.1 package, but when I run evil-winrm we still get the famous error. So, it still refers to the OpenSSL 3.0 config file. |
If you take a look at evil-winrm gemspec https://github.com/Hackplayers/evil-winrm/blob/381b126d6a8dc3ca38f7fab73cb80175fcbe8d45/evil-winrm.gemspec#L27, it relies on the winrm gem. I suggest you open a bug request upstream for openssl 3.0 support. |
Opened to WinRb/WinRM#340 |
By reading WinRb/WinRM#340, I think we can make a workaround.
or maybe better so there is no need of openssl 1.1.1
|
Fixing the issue linked in #3593 by enabling legacy protocols that Evil-WinRM uses for attacking the target machine. The issue is solved by enabling the legacy protocols after the pkg installation that have been kept disabled by default by OpenSSL maintainers with the latest OpenSSL version.