-
Notifications
You must be signed in to change notification settings - Fork 191
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
Proxyman CA cert doesn't have Server Authentication ( 1.3.6.1.5.5.7.3.1 ) OID
which is required by macOS 10.15
#367
Comments
Hey @TingluoHuang Proxyman is already updated with new Apple's requirements, but there is a missing of |
Hey yo @TingluoHuang Let check this BETA build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.13.0_Update_macOS_Certificate_Requirement.dmg Changelogs
Please open Help menu -> Debug -> Reset all Certificate & Data to completely remove the old one. Then you can install the new certificate 👍 Please let me know if it works since I couldn't test your case in my local machine. Thank you in advance 🌮 |
@NghiaTranUIT thanks for taking look at this. Server cert generated by proxyman:
Server cert generated by Fiddler:
As you can see the Fiddler cert contains:
How do you generate server certificate for each https request? I think you might need to do something like: |
I see, the absent is also from the Certificate, which is generated by Proxyman, not just only the Root Proxyman Certificate. I'm on it now 👍 |
Here is the updated @TingluoHuang https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.13.0_Missing_extension_certificate.dmg Please "Reset all Certificate & Data" before testing since there are cached certificates. Let me know if it works then I could release a 1.13.1 build 👍 Thank you in advance 🎉 |
@NghiaTranUIT it work, thanks! |
Glad to know that. Let update to Proxyman 1.13.1, which officially includes the fix 👍 |
Proxyman version? (Ex. Proxyman 1.4.3)
1.13.0
macOS Version? (Ex. mac 10.14)
10.15.2
Steps to reproduce
Check Proxyman CA cert details in keychain
Expected behavior
The CA cert has extended key usage
Server Authentication ( 1.3.6.1.5.5.7.3.1 )
According to https://support.apple.com/en-us/HT210176 and http://blog.nashcom.de/nashcomblog.nsf/dx/more-strict-server-certificate-handling-in-ios-13-macos-10.15.htm?opendocument&comments
When use proxyman with dotnet core app, dotnet core can't validate the server ssl cert via native macOS system call when proxyman decrypt SSL traffic.
dotnet/runtime#666
Screenshots (optional)
Other proxy server CA cert has this field (Fiddler)
The text was updated successfully, but these errors were encountered: