Dynamic tunneling is a transparent mechanism available for applications that support the SOCKS4 or SOCKS5 client protocol. Instead of configuring port forwarding from specific ports on the local host to specific ports on the remote server, you can specify a SOCKS server which can be used by the user's applications. Each application is configured in the regular way except that it is configured to use a SOCKS server on a localhost port. The Secure Shell client application opens a port in the localhost and mimics a SOCKS4 and SOCKS5 server for any SOCKS client application.
When the applications connect to services such as IMAP4, POP3, SMTP, HTTP, and FTP, they provide the necessary information to the SOCKS server, which is actually the Secure Shell client mimicking a SOCKS server. The client will use this information in creating port forwarding to the Secure Shell server and relaying the traffic back and forth securely, as with user-specified port forwarding.
For more information, please see the ssh2 man pages.
Cryptomining with the SSH protocol: what big enterprises need to know about it
Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency. Read more
SLAM the door shut on traditional privileged access management
Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity? Read more
We broke the IT security perimeter
Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so. Read more