mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 08:35:53 +03:00
[GH-ISSUE #1370] SSL Handshake Failed #1365
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#1365
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 @ghost on GitHub (Sep 25, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1370
Description
SSL decryption failed
Steps to Reproduce
1.Install the Proxyman Certificate on Your iOS Device
2.Enable SSL kill switch
3.Launch the app and enable decryption
4.fail to decrypt
Current Behavior
Unable to decrypt SSL
Therefore, you cannot view the contents of the communication.
Expected Behavior
Decrypt SSL successfully to view data
Environment
@NghiaTranUIT commented on GitHub (Sep 26, 2022):
Does it seem that SSL Kill Switch doesn't work? 🤔 @KohnoseLami
SSL Handshake failed because the app, which supports SSL Pinning, rejected Proxyman CA Certificate. You use SSL Kill Switch to bypass it, but I'm not sure if you properly config it.
@ghost commented on GitHub (Sep 26, 2022):
I tested it under the following three conditions.
The same error was output under all conditions.
Is this due to SSL Pinning rather than Proxyman certificate error?
When I tried it with the same application in the past, it worked once, but it didn't work when I tried it again.
If you drop the version of the application, it won't change.
@NghiaTranUIT commented on GitHub (Sep 26, 2022):
100% gets SSL Error because the certificate is not installed.
Which app are you trying to intercept? If it's a well-known app, such as Facebook, or Instagram, ... it's SSL Pinning.
Not sure if the SSL Kill Switch Config is correct. If it's not right, the SSL Error can occur.
@ghost commented on GitHub (Sep 26, 2022):
The app is called CapCut. This is an app made by Bytedance, a TikTok company, so there is a possibility that SSL Pinning exists.
However, since what I want is WebSocket, there is very little information on these.
@maximebories commented on GitHub (Sep 28, 2022):
It happens, and I'd say there is a 99% probability that this is because of a SSL pinning mechanism.
Now if you really want to be sure (but is it worth it ?), you could install the Frida.re framework and after digging a little you will find a SLL pinning library or retrieve a debug log which would confirm that. I haven't used it for ages but from memory it also allowed few people to bypass some SSL pinning mechanisms. Frida is easy to install on Android or a jailbroken iPhone, it's feasible but way more annoying on a non-rooted iPhone.
I don't know what your end goal is here, but I saw there is a web version of the app, maybe it's worth investigating...
Good luck
@chhpt commented on GitHub (Sep 28, 2022):
I've had some similar situations (with certificates installed and SSL Pinning turned off) where some domains would report an error and others would not, and after restarting Proxyman or the App it might be back to normal again
@NghiaTranUIT commented on GitHub (Sep 28, 2022):
Can you provide some information? Is it an iOS/Android app? Native, ReactNative, Flutter 🤔
@ghost commented on GitHub (Sep 28, 2022):
I used Frida once, but it was very difficult and difficult.
For this reason, I used the SSL kill switch, but many applications do not work correctly.
I didn't know that there was a desktop app, that there was a web version.
My research is insufficient.
That information is likely to help me a lot. Thank you!
@ghost commented on GitHub (Sep 28, 2022):
The same thing happened to me in CapCut.
Therefore, we are currently experimenting based on the communication captured in the past.
However, because of the missing information, I need to capture it again, but I am already in a situation where I cannot do it.
@ghost commented on GitHub (Sep 28, 2022):
When I checked the Web version, the required functions were reduced, so when I installed the Windows software, I found the required functions, so I connected the whole Windows through Proxyman and installed the certificate, and I was able to capture the Websocket successfully.
Now that I've solved my problem, I'm going to quote and close this post.
Thank you!