<br><br>
<div><span class="gmail_quote">On 1/30/06, <b class="gmail_sendername">Jeremy Fowler</b> <<a href="mailto:JFowler@westrope.com">JFowler@westrope.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Well, I think the only security reason to run an http server on a port other than 80 is to hide it from the general public. Port scanners can get around this hurdle quite easily though. Plus, the fact that you SNAT port 80 to that
</blockquote>
<div> </div>
<div>"Security through obscurity" isn't. The obscurity just makes it difficult for you to administer it. Put the stupid thing on port 80, do the split DNS that serves the internal IP to the internal machines, and if the internal IP must be changed, change it in DNS. What's the big deal?
</div><br> </div>