I recently created a bugreport for hyperscan (https://github.com/01org/hyperscan/issues/14) with some VS / x86 compilation fixes.
I just wanted to know what the status on this one is. It would be great, if someone could have a look and the more straightforward patches could get applied, so that we can reduce our diff. I'm happy to address any requests for changes/improvements or concerns.
One thing I noticed was that offsets, limits are always 64 bit. Is there a specific reason to not use a size_t? Using size_t could fix most of the alignment issues (passing aligned 64 bit values as parameters on x86).
We are very pleased to announce that the Suricata IDS team have merged support for using Hyperscan as an MPM literal matcher - there have been occasional questions about Suricata support, so I thought I would share this with the list.
Suricata is an open-source network intrusion detection/protection system: http://suricata-ids.org/
Here is Suricata lead developer Victor Julien's call for testers, which includes instructions for configuring it to build against Hyperscan and use it for MPM matching:
If you give it a go, we would love to see some feedback on your experience!