There is, however, good news for all the Suricata users with Hyperscan trouble on non-SSSE3 CPUs: starting with Hyperscan 4.4.0, Suricata will (at least that is what I understood from the release notes and patches) select the appropriate default and prevent Hyperscan loading when inappropriate, which should obsolete the need to a separate "suricata-no-hs" package some of you have been using. This change will make it to 17.1.2 on a separate track. Testing looks good so far.