mirror of
https://github.com/ProxymanApp/proxyman-windows-linux.git
synced 2026-04-27 00:45:55 +03:00
[GH-ISSUE #524] Client Certificate #522
Labels
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxyman-windows-linux#522
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 (Jul 30, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/524
Originally assigned to: @kics223w1 on GitHub.
Description
Similar to https://github.com/ProxymanApp/proxyman-windows-linux/issues/507, we should implement the Client Certificate
How Client Certificate works?
Criteria
Similar to #507 , we should have a service to manage the client certificate and a class to represent the cllient certificate and store it in the user data folder with subfolder: client-certificates
Support import via P12 or Pem/Der and passphare (similar to #507 )
Client Certificate is using on this side: [Proxyman -> Real Server] and works with
HTTPS
WSS
If the current connection's Host & Port is matched with Custom Client Certificate -> use it
Support 0 is a wildcard

Write Unit Tests