mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #1078] Proxy man won't let connect to Mircrosoft remote desktop servers #1074
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#1074
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 @takasurazeem on GitHub (Nov 30, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1078
Proxyman version: 2.35.0 (23500)
macOS Version: 11.6.1 (20G224)
Steps to reproduce Start capturing traffic and then try to connect to your remote desktop server through Microsoft remote desktop tool. It won't connect, close the Proxyman and then connect to the server and then again can open Proxyman.
Expected behavior: Should connect.
Screenshots
@NghiaTranUIT commented on GitHub (Nov 30, 2021):
It seems that Remote Desktop Gateway rejects self-signed Proxyman certificates (SSL Pinning). Therefore, all web debugging proxy app could not intercept their HTTPS Traffic.
I will double-check and get back to you 👍
@NghiaTranUIT commented on GitHub (Dec 1, 2021):
Confirmed @takasurazeem. This app is using SSL Pining, which prevents all MitM apps to capture their HTTPS Traffic. As a result, there is no solution to bypass it unless you have a pinned certificate 👍
@takasurazeem commented on GitHub (Dec 1, 2021):
@NghiaTranUIT how do we pin a certificate?
@NghiaTranUIT commented on GitHub (Dec 2, 2021):
@takasurazeem If you're a developer of this app, you will have a Pinned Certificate. Then you can add it as a Custom Server Certificate from Certificate Menu -> Add Custom Certificate 👍
If you don't have the certificate, there is no way to bypass it.