Hello George, Wednesday, February 16, 2005, 9:38:41 PM, you wrote:
GG> Even if someone doesn't use RDJ, isn't a 2-10 line commented change log GG> in the cf file worthwhile? GG> RDJ is not just for people who want to submit full trust. It can also GG> be used to help automate distribution of fully validated enterprise GG> rulesets, which happens to be the way I use it to distribute rulesets to GG> my clients and is why I've been working with Chris Thielen to develop GG> RDJ2, for better enterprise support and features that will help RDJ GG> scale to support enterprise, and more clients and ruleset servers. GG> #@@# A note specifying the recent changes made, with a comment designed GG> #@@# for grep-ing would be useful for the casual RDJ user to monitor GG> #@@# what automatic updates are doing, as well as function to notify the GG> #@@# enterprise admin of the changes he needs to validate, and integrate GG> #@@# with his private rules. GG> If you are going through the trouble of publishing your rulesets for GG> the ease of others to use, I don't see the point of forcing them to GG> submit trust or manually discover changes when you publish them. Fair enough. In this most recent publication of updates to the 70_sare_header*.cf family, 40 rules were added, and 50 rules were moved from one file to another, including 8 or 9 that were moved from various files to the archive file. How would you structure a change history for those changes? Bob Menschel
