mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #116] Support custom Certificate for Pining Certificate #112
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#112
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 @NghiaTranUIT on GitHub (Apr 12, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/116
Originally assigned to: @NghiaTranUIT on GitHub.
🐶 Brief
It's crucial to support Custom SSL Certificate for the domain, which is supported by SSL-Pinning.
For instance, Toggl Desktop is using custom Certificate for SSL, so it's impossible to intercept data unless debugging in Debug version.
It's time to support it.
👑 Criteria
@ptrkstr commented on GitHub (Apr 22, 2020):
Hi @NghiaTranUIT, did there happen to be any update on this?
I'm running into the use case where certificate pinning is implemented in an application and in order for testing to occur between multiple testers, we wish to distribute the same certificate between all instances of proxyman.
@NghiaTranUIT commented on GitHub (Apr 22, 2020):
Hey @patrickbdev I did a research but not sure how to implement this feature from last year. I will research again push this ticket forward and support it next releases soon 👍
@ptrkstr commented on GitHub (Apr 23, 2020):
Another question @NghiaTranUIT , is the certificate unique per Proxyman installation or is it the same across?
@NghiaTranUIT commented on GitHub (Apr 23, 2020):
If you mean the "Certificate" is Proxyman CA Certificate, it's a unique cert, which is locally generated in your machine
@NghiaTranUIT commented on GitHub (Jun 17, 2020):
Good news that I successfully set up local HTTPS with a self-signed certificate. It's the environment to test the Custome Certificate feature that I'm working on 🙌
One question @patrickbdev. What is the format of your certificate? PEM or P12?
@ptrkstr commented on GitHub (Jun 17, 2020):
You legend @NghiaTranUIT !
P12 is what I tend to use.
I notice that Charles supports both:
@NghiaTranUIT commented on GitHub (Jun 17, 2020):
Just wondering: Which feature do you use? Server Cert or Client Cert or Root Cert 🤔
@ptrkstr commented on GitHub (Jun 18, 2020):
Sorry for the late reply @NghiaTranUIT, I wasn't able to get it successfully working, but I believe the root certificate is what I need to change.
I guess whatever allows me to achieve this:
@NghiaTranUIT commented on GitHub (Jun 18, 2020):
I set up a local self-signed HTTPS server for testing the SSL-Pinning and I confirm that both Root Certificate and Server Certificate are working well as long as we have correct P12 or PEM files (private and cert) 👍
@ptrkstr commented on GitHub (Jun 18, 2020):
That’s great @NghiaTranUIT, I appreciate the effort!
@NghiaTranUIT commented on GitHub (Jun 26, 2020):
Hey @patrickbdev @joanbono, @tobiastom, and @finnsch , here is the good news 🎉
Let check out this BETA build of Custom Certificate:
Download: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.0.1_Custom_Certificate_v2.dmg
Doc: https://docs.proxyman.io/advanced-features/custom-certificates
@NghiaTranUIT commented on GitHub (Jun 28, 2020):
Just friendly reminder @patrickbdev @joanbono, @tobiastom, and @finnsch that Proxyman 2.1.0 is released with this feature 👍
Let check it out: https://github.com/ProxymanApp/Proxyman/releases/tag/2.1.0
@zhangjs commented on GitHub (Mar 2, 2022):
Can proxyman use the corresponding server certificate based on the domain name?
@NghiaTranUIT commented on GitHub (Mar 2, 2022):
Hey @zhangjs at the moment, if you provide a Custom Server Certificate, it will use it for all domain names. If you use the Custom Client Certificate, it will support a domain in the Common Name attribute 👍
@zhangjs commented on GitHub (Mar 2, 2022):
I added the correct server certificates for the domain names, but not the root ca, and it prompts the error "The operation couldn’t be completed. (Could not generate dynamic certificate from :443 error 999.) (code=999)"
@NghiaTranUIT commented on GitHub (Mar 2, 2022):
Have you added your custom certificate to Keychain access and trust it?
You can check out this section: 7. Import as a Custom Root Certificate at https://docs.proxyman.io/advanced-features/custom-certificates#7.-import-as-a-custom-root-certificate
@zhangjs commented on GitHub (Mar 2, 2022):
The doc says the client certificates "Use this certificate for SSL-Handshake to specific Server", "SSL-Handshake to your Clients" is what i need, I have the correct server certificate.
@zhangjs commented on GitHub (Mar 2, 2022):
I have the correct certificates, I don't want to trust self-signed Root Certificate
@zhangjs commented on GitHub (Mar 2, 2022):
I need proxyman use the corresponding server certificate to handshake the clients based the domain, not generate dynamic certificate.
@zhangjs commented on GitHub (Mar 2, 2022):
I need intercepting HTTPS Traffic from clients that use SSL-Pinning, Proxyman use the corresponding server certificate based on the domain name is what I need.