Is there any matrix of the new lua parsers and the old parser(s) they replace? Some of them are obvious, others less so. Anybody have experience switching over?
> In regards to the packers lua parser, you indicate it replaces the existing
> packers parser. Does this include all of the malware_packers_X parsers
The 'packers' flex parser file actually contains all of the individual malware_packers_X parsers. The 'packers' lua parser replaces all of them.
Our product engineer and Lua expert said he'd get you some more substantive detail later in the day but for now he had some quick notes:
* most parsers have the same name, just with "_lua" appended * a few were renamed for clarity, e.g. "pkware" -> "fingerprint_zip" * a few were combined into a single lua parser, e.g. "fingerprint_jar" and "fingerprint_java_class" were combined into "fingerprint_java"
* most parsers have the same name, just with "_lua" appended
* a few were renamed for clarity, e.g. "pkware" -> "fingerprint_zip"
* a few were combined into a single lua parser, e.g. "fingerprint_jar" and "fingerprint_java_class" were combined into "fingerprint_java"
Not all of the listed lua parsers are in Live yet, but will be.
This is great information - as there is no Matrix that I have found and simply configuring a new LUA parser does not automatically deprecate the equivalent flex parser. Please keep this list updated as LUA parsers continue. Also - some questions regarding your list as I have gone through this exercise:
bittorrent_lua - doesn't exist
botnet_lua - doesn't exist
DNS_verbose_lua - doesn't exist
fingerprint_pdf_lua - does this also replace malware_pdf_v201?
fingerprint_php_lua - doesn't exist
fingerprint_key - doesn't exist
htran_lua - doesn't exist
IRC_verbose_lua - does this also cover irc-expanded?
As of this writing I was not able to search the above lua parsers (those indicated as doesn't exist).
Not all of the listed lua parsers are in Live yet, but will be soon. Several were posted to Live on Friday.
For fingerprint_pdf_lua: yes (malware_pdf and malware_pdf_v201 are the same thing)
For IRC_verbose_lua: yes - I missed including irc-expanded in the list
That should cover nearly all of the existing flex parsers in Live, except for some website-specific parsers that will likely be converted in a more generic form, and some that won't be converted at all (e.g., "tcp-flags"). Many of the native parsers will eventually have lua equivalents, but those will be slower in coming.
Another I missed:
mail_lua also replaces email-ip
Can the source of the lua parsers be viewed directly?
It would be very helpful to reference these when creating my own parsers.
Currently they are all encrypted.
There will be some made available in some manner as unencrypted for demonstration purposes. But I don't yet know which, when, or how.
Thanks for your response.
Any word on the availability of some of these parsers unencrypted, for demonstration purposes? It would be useful for custom parser creation.
Is there any update to table? we're trying to apply the LUA parser but don't know which one to apply.
1. Can LUA parser and Flex parser be applied at same time?
2. Some Flex parsers don't have replacement LUA parser, like OS and browser parser, when will it be available?
Sorry for the late reply.
1. Yes, they can be enabled at the same time. But if a flex and a lua parser that parses the same thing are both enabled, then the decoder will be doing more work and registering duplicate meta.
2. Those two parsers really just tried to match bits of user-agent headers and make inferences based on that. Instead HTTP_lua simply registers the entire user-agent header.
if like this, can the system auto detect if both flex and lua pasers enabled for the same thing, it will disable one of them?
That would be nice, but it doesn't do that currently.
Now that HTTP_lua is available and replaces NTLMSSP does it also replace NTLMSSP_lua?
Correct, if you have HTTP_lua enabled you shouldn't need NTLMSSP_lua as well.
will it become a KB link？
Great information! Is there an easy way to remove the old flex parsers, or is it a manual/scripted process?
> Great information! Is there an easy way to remove the old flex parsers, or is
> it a manual/scripted process?
Its a manual process for now unfortunately.
Retrieving data ...