|
From: Christian F. <chr...@ne...> - 2016-06-19 18:47:24
|
Hello Walter, On Sun, Jun 19, 2016 at 05:41:47PM +0200, Walter Hop wrote: > > With 200K range assigned to Comodo, the case is even weirder. The ModSec > > project itself is definitely distributing rules in this range in: > > https://github.com/SpiderLabs/ModSecurity/blob/master/modsecurity.conf-recommended <https://github.com/SpiderLabs/ModSecurity/blob/master/modsecurity.conf-recommended> > > Current version of Comodo’s rules starts at id 210000 right now. So this would be a typo then. Would make sense. Thank you for the info. Have not had the Comodo rules in my hand... (But I can confirm Atomicorp is sticking to their range with one exception. Sent them a message.) Ahoj, Christian > > I don’t have any contacts with their developers, but if they would agree to keep working at 210000 and higher, we could legalize the de facto use of 200xxx by modsecurity.conf (which will be widespread for lots of years anyway): > > 200000-200999: ModSecurity > 210000-299999: Comodo > > -- > Walter Hop | PGP key: https://lifeforms.nl/pgp > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports. http://sdm.link/zohomanageengine > _______________________________________________ > mod-security-developers mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-developers > ModSecurity Services from Trustwave's SpiderLabs: > https://www.trustwave.com/spiderLabs.php -- mailto:chr...@ne... http://www.christian-folini.ch twitter: @ChrFolini |
