lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20031118144914.7b95f75f.michael@bluesuperman.com>
From: michael at bluesuperman.com (Michael Gale)
Subject: Sidewinder G2

So if you have a HTTP application level proxy does that mean you are
running a webserver ?

This is how proxies work, they respond to the client, then check the
packets being sent or received. Then the proxy connects to the server on
your behalf.

You should read up on application level filtering and firewall.

The BorderWare Firewall is almost completely based on the application
level proxies, as well as circuit level and packet level.

The firewall has proxies for http, ssh, telnet, smtp, ICQ -- by your
definition the firewall is running a web server, sshd, telnet daemon,
mail server and a ICQ server.

Michael.


On Tue, 18 Nov 2003 23:40:57 -0500
Valdis.Kletnieks@...edu wrote:

> On Tue, 18 Nov 2003 14:32:04 MST, you said:
> > 
> > Application level proxies - So the proxy can respond even if the
> > internal mail server is down.
> 
> Right.  AND IF ITS RESPONDING, ITS ACTING AS AN SMTP SERVER.
> 
> It might not be the main mail hub, but it's STILL an SMTP server,
> which is *ANYTHING* that pretends to follow the "server" end of
> the protocol defined in RFC821/2821.
> 



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ