This can be useful in several testing scenarios. With a SOCKS proxy established over SSH, traffic can then be tunneled through the connection so that it exits from the remote end of the proxy connection. Secure Shell (SSH) has the ability to set up a SOCKS proxy when connecting to a remote server with the added benefit that all of the traffic being sent over the connection is encrypted via the SSH protocol.
SOCKS connections allow for the redirection of specific traffic through the established proxy in order to have more control over how the traffic is being handled. This means that a connection is established between two nodes or hosts and traffic flows into the tunnel established between those hosts. If you're unfamiliar, SOCKS is a protocol that sends traffic between two endpoints via a proxy. Today, I'm only going to cover one feature that you should consider when using Burp for web application testing, SOCKS proxying. Due to it's rich feature set, and all of the additional capabilities that are available via the Extender, tool and the BApp store, Burp can quickly become overwhelming for an inexperienced tester. It's far from a "fire-and-f0rget" tool, which means that it take a lot of getting used to in order to make effective use of everything that the tool has to offer. There's no question about it, PortSwigger's Burp Suite is the de-facto tool for testing web applications for security vulnerabilities.
0 kommentar(er)
