[
https://www.modsecurity.org/tracker/browse/CORERULES-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Barnett resolved CORERULES-86.
-----------------------------------
Resolution: Invalid Config
Had to list the latest version in the repo listing.
> CLONE - Rules-updater script fails to retrieve latest release from source
> forge repository
> ------------------------------------------------------------------------------------------
>
> Key: CORERULES-86
> URL: https://www.modsecurity.org/tracker/browse/CORERULES-86
> Project: Core Rules
> Issue Type: Bug
> Security Level: Normal
> Components: Configuration
> Affects Versions: 2.3.0
> Environment: Windows 2008 Server, Apache 2.2 64bit and Mod_security
> from http://www.apachelounge.com/download/win64/
> Reporter: Jason Huntley
> Assignee: Ryan Barnett
> Labels: rules, rules-updater, script, updater
>
> Rules-updater script fails to download latest release. Fails on error:
> $ ./rules-updater.pl -rhttp://www.modsecurity.org/autoupdate/repository
> -prepository/ -Smodsecurity-crs
> Could not load GnuPG module - cannot verify ruleset signatures
> Fetching: modsecurity-crs/modsecurity-crs_2.2.3.zip ...
> Failed to retrieve ruleset modsecurity-crs/modsecurity-crs_2.2.3.zip: 404 Not
> Found
> There's also a new release out 2.2.4. For some reason, the script is also
> still trying to pull the old release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
[email protected]
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set
