Support for PCRE2 about vectorscan HOT 4 OPEN

Hi, a migration to the new library should be done, it's in the TODO list. Will close this ticket when the migration is done. Apologies for the inconvenience.

from vectorscan.

From some research on migrations to pcre2, this will probably create incompatibilities with hyperscan 5.4, so we will have to create a migration plan and also add an Vectorscan specific API/ABI version string for applications to check. It will be moved to next milestone.

from vectorscan.

At Suricata we've switched to pcre2 in our latest major release, and we've not really noticed many issues. The only one was that pcre2 is by default more picky about "invalid escapes". I later found this flag PCRE2_EXTRA_BAD_ESCAPE_IS_LITERAL (https://www.pcre.org/current/doc/html/pcre2_set_compile_extra_options.html) which would probably have fixed those issues. Just FYI.

from vectorscan.

@victorjulien ok, that's good to know, from reading the manuals I was under the impression that there will be many cases where user input might be needed to change, which is the problem basically. It's one thing to change the function calls and quite another to introduce an incompatibility because of a difference in the library, perhaps a period where both versions might be supported should be the best solution.

from vectorscan.