Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SSL keylogfile support for advanced network troubleshooting #2037

Open
skyhirider opened this issue Apr 8, 2024 · 3 comments
Open

Add SSL keylogfile support for advanced network troubleshooting #2037

skyhirider opened this issue Apr 8, 2024 · 3 comments

Comments

@skyhirider
Copy link

Bruno could support SSLKEYLOGFILE so that network monitoring and troubleshooting tools like Wireshark could be used with it.

Use case:
I was setting up oauth credentials and the requests were failing. The window in Bruno did not show me the request and response flow as it was inside the authentication tab, so I had no way to properly troubleshoot. I needed to know the exact url that was queried as well as the payload and server response, but it was nowhere to be found.

I figured I could intercept the traffic via Wireshark like I can do with Chrome via the SSLKEYLOGFILE that allows the intercepted traffic to be decrypted locally so that I can inspect what is going wrong.

Nope, Bruno dues not support that even thou it is running Chrome version 106.

Is this something that could be added or enabled? Maybe its just one switch you need to toggle in Electron.

@PushpenderSaini0
Copy link
Contributor

Even i had similar issue with the oauth , were you using client credential ?

It was a small fix that has been merged here !

  • This will be released in the next version .

Also if you wish to examine the calls made by bruno i think something like wireshark is overkill.

You could easily use a proxy and debug your traffic there, i have used this to fix the auth issue above !

@skyhirider
Copy link
Author

For me the issue was that I put in the url with the unique oauth string a the and as well, and Bruno was probably appending it again.
Would be an easy fix if I could see what request was sent and which url was used, but there was no way to find it.
Resorted to Wireshark in the end, but that did not help as I could not decrypt the message either.
Was by dumb luck I tried a shorter url. Wasted time on this, time I could have spend on something else :(

@PushpenderSaini0
Copy link
Contributor

You can use a simple proxy tool like https://httptoolkit.com/ as a proxy to check what calls are being made by bruno.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants