Hi Patrik,<br><br>I think you might find this useful then:<br><br><a href="http://doxygen.openinfosecfoundation.org/">http://doxygen.openinfosecfoundation.org/</a><br><br><a href="https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Suricata_Developers_Guide">https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Suricata_Developers_Guide</a><br>
<br><br>How is the flow handled for ex:<br><a href="http://doxygen.openinfosecfoundation.org/structFlow__.html">http://doxygen.openinfosecfoundation.org/structFlow__.html</a><br><br>Any of the Dev gentlemen , please correct me if I am wrong (since I am not a coder)<br>
<br>Thanks<br><br><div class="gmail_quote">On Fri, Jul 27, 2012 at 1:47 PM, Pratik Narang <span dir="ltr"><<a href="mailto:pratik.cse.bits@gmail.com" target="_blank">pratik.cse.bits@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
Can anyone please help me out with Suricata's architecture-  based on their<br>
own knowledge, or documentation or books or references available for<br>
it.<br>
I wish to understand the architecture at a high level of abstraction<br>
and understand the various modules, their dependencies, what part of<br>
the source code does what, where does the signature engine lie, where<br>
is the anomaly engine, etc.<br>
<br>
Thanks<br>
_______________________________________________<br>
Oisf-users mailing list<br>
<a href="mailto:Oisf-users@openinfosecfoundation.org">Oisf-users@openinfosecfoundation.org</a><br>
<a href="http://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users" target="_blank">http://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div>Regards,</div>
<div>Peter Manev</div><br>