mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 00:55:57 +03:00
[GH-ISSUE #1671] Support TLS key logging #1664
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#1664
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 @seidnerj on GitHub (Jun 7, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1671
Originally assigned to: @NghiaTranUIT on GitHub.
Description
Support TLS key logging, this can be implemented by Proxyman looking for a "SSLKEYLOGFILE" environment variable as is done in other applications or by some other means (UI-wise).
Why this feature/change is important?
I am trying to debug issues that seem to origin in the communicate between Proxyman and the target server, I am using Wireshark to look at the relevant traffic but unfortunately (in this case) it is encrypted (TLS), if the keys could be logged as in other applications, I could then load them to Wireshark and take a look at the unencrypted traffic. Without this, I have no insight into what is happening between Proxyman and the target server.
@NghiaTranUIT commented on GitHub (Jun 8, 2023):
Thanks for opening the ticket. I might consider to implement this feature if we collect more requests 👍
@swznd commented on GitHub (Sep 20, 2023):
agreed, I have similar issue, I need to compare request between app to proxyman and proxyman to target server
@dabing1022 commented on GitHub (Jun 1, 2024):
June 1, 2024. Excuse me, is it supported now?
@novitae commented on GitHub (Jan 8, 2025):
Any news ? @NghiaTranUIT
@NghiaTranUIT commented on GitHub (Jan 8, 2025):
@novitae To be honest, I don't know how to implement it. Can you show me the current solution from another app?
@novitae commented on GitHub (Jan 8, 2025):
I just took a look at how mitmproxy does it, but their backend is python, so it will be different for you.
What crypto backend are you using ? OpenSSL ? If it is, or any other big one, I'm pretty sure it's easy and there are already methods to make it easier. I am willing to do the researches !
@NghiaTranUIT commented on GitHub (Jan 8, 2025):
@novitae It's what you're looking for?
@novitae commented on GitHub (Jan 8, 2025):
Yes usually you have to log both
@NghiaTranUIT commented on GitHub (Jan 8, 2025):
thanks. I will add it. What do you do with this file? These secrets don't link with certain domains, so It's hard to know which domain SSL is.
@novitae commented on GitHub (Jan 8, 2025):
Yes I must admit the way it works I a bit confusing, and I couldn't explain to you how it works to find which key is for which connection, but read this you might understand better:
https://wiki.wireshark.org/TLS#Using%20the%20(Pre)-Master-Secret
@NghiaTranUIT commented on GitHub (Jan 11, 2025):
@novitae @dabing1022 @swznd @seidnerj Good news: TLS Key Logging is officially supported on this Beta build: https://download.proxyman.io/beta/Proxyman_5.12.2_Support_TLS_Key_Logging.dmg
You can access it in the Tool menu -> TLS Key Logging -> Select your File or Folder.
SSLKEYLOGFILE@novitae commented on GitHub (Jan 11, 2025):
Thank you ! I just tried it and decrypted with Wireshark, it works perfectly
@seidnerj commented on GitHub (Jan 11, 2025):
This is awesome!!! Thank you so much @NghiaTranUIT! 🙏