I notice the "www.snort.org/pub-bin/oinkmaster.cgi" script has some form
of download limiting component (to stop people like me repeatably
downloading the same live data while editing/updating local scripts - ahem).
Anyway, such scaling issues happen. I'd like to suggest that Sourcefire
look to ClamAV to see how they handled people hammering their servers
looking for updates that didn't exist (i.e. they were already up to
date). Their rules basically have a serial number and they put that into
a DNS record, and then their freshclam update daemon looks to that DNS
record before deciding to actually do a HTTP connection to download an
update. Than plus some time-of-day randomization and load sharing should
go a loooong way on the scalability side...
Just an idea.
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users
