Re: which firewall

From: Jens Hoffmann (jh@bofh.de)
Date: 05/27/02 

From: jh@bofh.de (Jens Hoffmann)
Date: 27 May 2002 21:42:53 GMT

Hi,

>> You have to let requests through to port 80 right?

Not neccessarily. Take a reverse proxy.
This will at least ensure syntactically correct questions to the webserver
behind it.

IIS as webserver is bad, if you can reach it directly ,)
If you just ask the right questions, there will be only correct
answers. (Hahaha.)

Greetings,
   Jens

Relevant Pages

  • Re: which firewall
    ... Take a reverse proxy. ... This will at least ensure syntactically correct questions to the webserver ... IIS as webserver is bad, if you can reach it directly,) ...
    (comp.security.firewalls)
  • Re: which firewall
    ... Take a reverse proxy. ... This will at least ensure syntactically correct questions to the webserver ... IIS as webserver is bad, if you can reach it directly,) ...
    (comp.security.firewalls)
  • Re: which firewall
    ... Take a reverse proxy. ... This will at least ensure syntactically correct questions to the webserver ... IIS as webserver is bad, if you can reach it directly,) ...
    (comp.os.ms-windows.nt.admin.security)
  • Re: Page Cannot Be Displayed Errors
    ... It sounds like you are quite close to the webserver. ... need to connect directly to IIS) ... If you see requests in the network monitor ... There is a network monitor included in Windows Server 2003 (not sure about ...
    (microsoft.public.inetserver.iis)
  • Re: How to secure a webserver in a DMZ
    ... If your webserver gets comprised, your DB is open as well. ... How easy would it be for an "advanced agressor" to load evil code (for ssh-over-https-tunneling i.e.) from the internet, if the only connection to the webserver is encrypted http inbound and outbound traffic is not allowed? ... If anybody was able to compromise the Reverse proxy over https, than he could even go further and compromise the backand webserver through tricky-http stuff also? ...
    (Security-Basics)