Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

WireGuard mode in mitmproxy where find client config file? How work with it? Any documentation? #6822

Closed
Vasa211 opened this issue Apr 27, 2024 · 1 comment
Labels
kind/triage Unclassified issues

Comments

@Vasa211
Copy link

Vasa211 commented Apr 27, 2024

Problem Description

WireGuard mode in mitmproxy where find client config file? (not mitmweb in "mitmproxy --mode wireguard@1111")

Steps to reproduce the behavior:

  1. Look in ~./wireguard but nothing

System Information

Using last mitmproxy

And how it work? i cant find any documentation I need start wg too (with mitm), or setup some networks? what i need do for start mitmproxy in WireGuard mode on my server, share config to my iphone and see all requests (get, post, put, patch)

@Vasa211 Vasa211 added the kind/triage Unclassified issues label Apr 27, 2024
@Vasa211 Vasa211 changed the title WireGuard mode in mitmproxy where find client config file? WireGuard mode in mitmproxy where find client config file? How work with it? Any documentation? Apr 27, 2024
@mhils
Copy link
Member

mhils commented Apr 30, 2024

You can find the WireGuard config in the mitmproxy/mitmdump event log (or straight in mitmweb). We still need to do some UI work here.

@mhils mhils closed this as completed Apr 30, 2024
@mitmproxy mitmproxy locked and limited conversation to collaborators Apr 30, 2024
@mhils mhils converted this issue into discussion #6824 Apr 30, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
kind/triage Unclassified issues
Projects
None yet
Development

No branches or pull requests

2 participants