This kind of lines up with the templating work that I've been working on.
First with binpac_quickstart, I just made the name uppercase:
https://github.com/grigorescu/binpac_quickstart/blob/master/templates/plugin_cc.jinja2#L8
The new version, CookieCutter (
../../zeek/bin/zeek -NN | grep -i net
output here, showing existing variation, so if there are nuances in points to
be discussed, we have actual examples to compare and contrast.
[Event] irc_network_info
Zeek::Login - Telnet/Rsh/Rlogin analyzers (built-in)
[Analyzer] Telnet
Short postscript here, because I just learned there is more than one namespace
involved, and that config.name in plugin.cc is probably where zeek -N picks up
the string that it utilizes:
The code has:
namespace plugin {
namespace Zeek_BACNET {
Plugin plugin;
}
}
using
I'm wondering if we simultaneously want to strongly guide the package name
capitalization, where for instance I see in the output of
/usr/local/zeek/bin/zeek -N | grep -i net
Zeek::Login - Telnet/Rsh/Rlogin analyzers (built-in)
Zeek::NetBIOS - NetBIOS analyzer support (built-in)
Zeek::BACNET -
Sounds good to me, unifying tags makes sense. The one thing I'd add is
a selection of standardized tags for general categorization, along the
lines of the existing:
https://docs.zeek.org/projects/package-manager/en/stable/package.html#suggested-tags
Probably best to start with extending that
