hi Matt<br><br>are these groups open to public ?<br><br>thanks<br>Jules<br><br><div class="gmail_quote">2009/7/24 Matt Jonkman <span dir="ltr"><<a href="mailto:jonkman@jonkmans.com">jonkman@jonkmans.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">As described in the meeting notes from DC, a great idea was put up to<br>
use working groups to discuss and explore ideas which haven't easy<br>
solutions. There are four working group lists setup. Each will need a<br>
leader and for most we're asking for volunteers.<br>
<br>
The group leader will be responsible for steering or sparking<br>
discussion, kicking any overtly disruptive posters, and steering toward<br>
a coherent outcome within the timeframes available. This is a pretty low<br>
maintenance position so please consider volunteering.<br>
<br>
Membership in each working group is open to anyone. These are on<br>
separate lists primarily to keep the main oisf lists from turning into<br>
spam engines. If you have any interest or anything you might be able to<br>
contribute to a discussion please consider hopping on and at least<br>
listening to each group.<br>
<br>
The groups setup are:<br>
<br>
1. IP Reputation<br>
I've taken lead on this group as it's near and dear to my heart. We'll<br>
be discussion the categories of reputation to track, methods, feedback<br>
vetting, etc.<br>
<br>
2. Non-Standard Acceleration<br>
The use of OpenCL or Cuda to accelerate the engine using standard<br>
graphics cards and chipsets.<br>
<br>
3. Rules Language<br>
This group will discuss the options for a new language in the future,<br>
whether the snort syntax would be extendable enough to support our new<br>
methods, and how to avoid major divergence. A secondary task will be to<br>
discuss whether to and how to offer rule obfuscation for rule writers<br>
that have legal requirements to not disclose vulnerability details.<br>
<br>
4. DDoS/Portscan<br>
This group will determine whether we need a new portscan preprocessor,<br>
and whether it would be feasible to build a new DDoS preprocessor.<br>
<br>
You can see all of these lists here along with more detailed descriptions.<br>
<a href="http://lists.openinfosecfoundation.org/mailman/listinfo" target="_blank">http://lists.openinfosecfoundation.org/mailman/listinfo</a><br>
<br>
We need group leaders for groups 2-4. Please email me directly if you're<br>
interested in helping out!<br>
<br>
Thanks!<br>
<br>
Matt<br>
<br>
<br>
--<br>
--------------------------------------------<br>
Matthew Jonkman<br>
Emerging Threats<br>
Phone 765-429-0398<br>
Fax 312-264-0205<br>
<a href="http://www.emergingthreats.net" target="_blank">http://www.emergingthreats.net</a><br>
--------------------------------------------<br>
<br>
PGP: <a href="http://www.jonkmans.com/mattjonkman.asc" target="_blank">http://www.jonkmans.com/mattjonkman.asc</a><br>
<br>
<br>
_______________________________________________<br>
Emerging-sigs mailing list<br>
<a href="mailto:Emerging-sigs@emergingthreats.net">Emerging-sigs@emergingthreats.net</a><br>
<a href="http://lists.emergingthreats.net/mailman/listinfo/emerging-sigs" target="_blank">http://lists.emergingthreats.net/mailman/listinfo/emerging-sigs</a><br>
</blockquote></div><br>