This is JB Cheng from Trend Micro and I provided OSSEC 2.7 release on ossec.net web site.
I will add a direst link on the Download page to the development repository, currently hosted at https://bitbucket.org/jbcheng/ossec-hids. On Friday, March 8, 2013 5:29:32 AM UTC-8, dan (ddpbsd) wrote: > > On Fri, Mar 8, 2013 at 3:37 AM, Ryan Schulze <[email protected]<javascript:>> > wrote: > > > >>> Even if I know where it is (and probably most other people following > the > >>> list) I suspect anyone that is considering using OSSEC in a production > >>> environment will want to stick with the stable releases found on the > >>> official website. > >>> > >> That seems like a flaw in their process. If they refuse to use the > >> source, why use open source? > >> > > No one said anything about not using sourcecode, but the only source you > get > > off the official website is 2.7 and no information about where to access > any > > development repositories. So as long as you stick to official > information, > > 2.7 is the most current you can get. > > I have no idea who is developing what in which repository and who's > > repository merges into official releases, so I write my patches against > 2.7. > > I may look around at what other people are doing, but as long as it > isn't an > > official beta or RC on the website, I'm not going to worry much about > what > > people do in their repositories. > > > > I will attempt to put this information in the documentation. I had > previously thought mentioning the repositories on the mailing lists > would be enough, because why would someone who won't pay attention to > the mailing lists want to modify the code? > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
