mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-29 01:55:51 +03:00
[GH-ISSUE #367] 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 #363
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#363
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TingluoHuang on GitHub (Jan 3, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/367
Originally assigned to: @NghiaTranUIT on GitHub.
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.
https://github.com/dotnet/runtime/issues/666
Screenshots (optional)
Other proxy server CA cert has this field (Fiddler)

@NghiaTranUIT commented on GitHub (Jan 3, 2020):
Hey @TingluoHuang
Proxyman is already updated with new Apple's requirements, but there is a missing of
TLS server certificates. I'm on it now 👍@NghiaTranUIT commented on GitHub (Jan 3, 2020):
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 🌮
@TingluoHuang commented on GitHub (Jan 3, 2020):
@NghiaTranUIT thanks for taking look at this.
I think we are 1 step closer. :)
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:
https://gist.github.com/fntlnz/cf14feb5a46b2eda428e000157447309#gistcomment-3098018
@NghiaTranUIT commented on GitHub (Jan 3, 2020):
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 👍
@NghiaTranUIT commented on GitHub (Jan 4, 2020):
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 🎉
@TingluoHuang commented on GitHub (Jan 4, 2020):
@NghiaTranUIT it work, thanks!
@NghiaTranUIT commented on GitHub (Jan 5, 2020):
Glad to know that. Let update to Proxyman 1.13.1, which officially includes the fix 👍