Hi,
On Fri, May 24, 2002 at 12:02:54PM +0200, Chand wrote :
> To "solve" in a way those two dilemmas we should have two things :
> - a way to log socket activity (src host, dest host, ips, user, script doing
>the 'attack', etc)
> - a way to blacklist ips (in a host.deny way) in the php.ini for example
As far as logging goes, I'm uncertain if it's a real benefit.
Right now fsockopen() is as good when it comes to TCP
connections and sending any kind of data.
And blacklisting is certainly a thing which belongs to
firewalls and not PHP.
my2cents,
- Markus
--
Please always Cc to me when replying to me on the lists.
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
---------------------------------------------------------
"I mean "When in doubt, blame mcrypt" is more often right than wrong :)"
"Always right, never wrong :)"
- Two PHP developers who want to remain unnamed
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
