Burp Suite User Forum

Create new post

Display status of SOCKS proxy and require SOCKS proxy

Micheal | Last updated: Jun 14, 2024 05:08PM UTC

This one is two-fold. Some of us have engagements that require more stealth, so we use the SOCKS proxy. However, more than once now I've had the SOCKS proxy be turned off when my VM crashes. To supplement that, I'd like to see: 1. A banner that shows if the SOCKS proxy is active or not in the Proxy tab 2. A checkbox or some other option to disallow any traffic until the SOCKS proxy is enabled This will hopefully prevent "accidents" in revealing our IP and the SOCKS proxy IP can be burned and rotated as needed.

Josh, PortSwigger Agent | Last updated: Jun 17, 2024 09:43AM UTC

Hi Michael, these sound like good ideas - we can get a feature request raised for you. We can't guarantee when this work will be prioritised, but we can get it logged which is a good start.

Michelle, PortSwigger Agent | Last updated: Jun 26, 2024 02:32PM UTC

We've been discussing this further here with the developers and researchers and after giving this very careful consideration we feel that this would better handled at the operating system level rather than within an individual application (i.e. Burp, in this case) as this gives you more control and therefore confidence in what will and won't be routed via specific interfaces/proxies at any point in time.

Micheal | Last updated: Jul 02, 2024 08:27PM UTC

Hi, Apologies for the delay, I didn’t see a notification. For Burp specifically, I’d like the SOCKS features. For the other applications/OS, I use proxychains so I have that control I’m looking for. But since Burp has its own SOCKS support, I’d like a bit more control over the communication.

Michelle, PortSwigger Agent | Last updated: Jul 03, 2024 01:59PM UTC

Thanks for getting in touch. This isn't something we've had other users requesting in the past. It's possible that some have similar thoughts to ourselves and have reservations about relying fully on Burp to protect against requests being accidentally sent and are using the OS level to handle this use case. I will share your latest feedback with the team though.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.