-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daryl C. W. O'Shea wrote: > Koopmann, Jan-Peter wrote: >> Hi, >> >> please excuse me if the archives already answer the question and I >> overlooked it. >> >> I am going to upgrade to 3.2.0 this week but remember reading that >> sa-compile will not work with SARE rules currently. If I understand it >> correctly when using sa-compile it will be used for all rules so you >> cannot use sa-compile for the "working" rules and have others not >> compiled? >> >> Therefore the question: Someone wrote all SARE rules would be updated >> these days so they are compatible with sa-compile. Is there some new >> status? > > 70_sare_stocks.cf is the only ruleset that has been updated since the > release of 3.2.0. I don't believe the update was to fix any UTF8 > issues, nor do I know if there are any issues with this ruleset. > > Daryl
No, the 70_sare_stocks.cf was re-scored and a couple rules were removed from it and had nothing to do with the UTF-8 issue. I've just about gotten the rule sets that are causing that issue fixed. Look for them in the next day or so. Of course, this all depends on other factors. 8*) - -- -Doc Penguins: Do it on the ice. 8:44am up 4 days, 16:55, 17 users, load average: 0.18, 0.30, 0.37 SARE HQ http://www.rulesemporium.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFGS4khqOEeBwEpgcsRAjfDAJ9sbli0jlFgKqQ4WoAPQpcqGKOCSACgjovy D5ivgPBXU8tovTrN3sBA9lA= =qzAK -----END PGP SIGNATURE-----
