Just for info i have setup a mirror of the modsecurity code and crs, years ago, under bazar on launchpad. It live under a my personal account , but it is public . The original modsecurity mirror on lauchpad point to a very old cvs repo , and the lauchpad admins did not want to update it. It is always in sync with the sf svn repo, thanks to the launchpad platform: so i am tracking the modsecurity development in real time from years :=).
Github don't offer a similar feature, but i prefer to use git Anyway. Best regards 2012/9/14, Ryan Barnett <rbarn...@trustwave.com>: > I wanted to update everyone to let them know that I have begun the process > of migrating the OWASP ModSecurity Core Rule Set from SourceForge (SVN) to > GitHub (git). > > Here is the current repo/data for testing - > > Landing Page - http://spiderlabs.github.com/owasp-modsecurity-crs/ > Git Repo - https://github.com/SpiderLabs/owasp-modsecurity-crs > > This initial commit to GitHub contains CRS v2.2.6 updates. If you want to > download packages archives, use these links: > https://github.com/SpiderLabs/owasp-modsecurity-crs/tarball/master > https://github.com/SpiderLabs/owasp-modsecurity-crs/zipball/master > > If you find any issues with the new CRS, please use the GitHub Issues > interface - https://github.com/SpiderLabs/owasp-modsecurity-crs/issues. > This will most likely replace our current Jira system for bug tracking. > > Keep in mind that we have only done this for the OWASP ModSecurity CRS and > not for the ModSecurity source code yet. We will be doing that in the > near future. > > Let me know if anyone has any issues/questions/comments. > > Other than that, I say GO FORTH AND FORK AWAY!!! I am really hoping that > this move will help to make community contributions easier. > > -- > Ryan Barnett > Trustwave SpiderLabs > ModSecurity Project Leader > OWASP ModSecurity CRS Project Leader > > > > > On 8/9/12 5:54 PM, "Ryan Barnett" <rbarn...@trustwave.com> wrote: > >>We are considering a migration of our ModSecurity source code and the >>OWASP CRS from sourceforge (SVN) to GitHub (git). >> >>There are many reasons why we are considering it but the most relevant >>one is enabling community contributions. I had a number of people tell me >>in person at Blackhat that if the project was moved to GitHub they would >>more inclined to contribute. >> >>If you agree or disagree with this rationale then please let me know. >> >>Thanks. >> >>-- >>Ryan Barnett >>Researcher Lead >>Trustwave - SpiderLabs >> > > > ________________________________ > > 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 > -- Inviato dal mio dispositivo mobile _______________________________________________ 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
