18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 123: Port<br />

redirection for inbound<br />

proxy<br />

Port redirection<br />

Chapter 9: Configuring Proxies<br />

Redirected proxy connections<br />

If you need to work around site-specific idiosyncrasies or to obscure the<br />

existence <strong>of</strong> a proxy for a given service, you can use port redirection. While<br />

such obscurity does not lessen the vulnerability resulting from something like<br />

an inbound Telnet proxy, it does reduce the number <strong>of</strong> attacks because the<br />

casual attacker might not notice it. Also, the attacker must take more<br />

conspicuous actions, like port scanning, to find the entry point. This makes it<br />

more likely that the administrator will notice the attack. Port redirection is<br />

implemented in the Source/Dest tab <strong>of</strong> the Rule window on a per-rule basis.<br />

See Chapter 8 for information on configuring port redirection.<br />

As an example, in Figure 123, suppose you want to configure a new proxy for<br />

an internal host that will provide Telnet service and accept external<br />

connections. In this configuration, a proxy connection arrives from the external<br />

network and connects to the external side <strong>of</strong> the <strong>Sidewinder</strong> <strong>G2</strong>. The<br />

connection arrives on the port named “hidenet” (port 5111). When this<br />

connection comes in, it will be proxied to the internal network, similar to how an<br />

address redirection is handled.<br />

Telnet server<br />

192.55.4.4<br />

Telnet port 23<br />

internal<br />

network<br />

redirect<br />

external<br />

network<br />

192.55.214.24<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

hidenet port 5111<br />

client Telnets to<br />

port 5111 on the<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

172.16.4.4<br />

The proxy redirects (remaps) the<br />

Telnet session to port 23 (but the<br />

port is concealed from the<br />

external network)<br />

The difference here is that the client on the external network connects to port<br />

5111 (hidenet) on the <strong>Sidewinder</strong> <strong>G2</strong> and the <strong>Sidewinder</strong> <strong>G2</strong> connects the<br />

client to port 23 (the standard Telnet port) on 192.55.4.4 host in the internal<br />

network. This permits an inbound Telnet connection to a host with a private IP<br />

address and does so on a port number that is not well-known for this service.<br />

This discourages so-called “door-knob rattlers.”<br />

249

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!