On 2/13/12 4:56 PM, "Christian Bockermann" <ch...@jwall.org> wrote: > > (4) Provide packages for RPM/Debian > > Josh and me had a discussion on "the perfect setup" a while ago, >thinking about the > best structure on how to setup ModSecurity rules and configurations. >Having a simple > structure provided within RPM and Debian packages would ease the >setup and could be > valuable as upgrade-tool as well. > From my perspective it would be perfect to follow Ivan's ModSecurity >Handbook in this > perspective (e.g. the /opt/modsecurity/ directory structure). > This could go hand-in-hand with signing the packages with official >GPG-keys. > > In addition to providing a ZIP/alternative package (e.g. for >Windows), of course.
I know that we already have some package manager folks (Jason Litka, Alberto Gonzalez Iniesta, etc...) handling the ModSecurity engine itself which are listed under the "Community-Produced Binary Packages" listing - http://www.modsecurity.org/download/ Maybe we can discuss this with them. -Ryan This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. _______________________________________________ Owasp-modsecurity-core-rule-set mailing list Owasp-modsecurity-core-rule-set@lists.owasp.org https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set
