zeek/scripts/base/frameworks/netcontrol
Jon Siwek 613b27eec7 GH-1080: Rename conflicting NetControl::DROP enum definitions
``NetControl::DROP`` had 3 conflicting definitions that could potentially
be used incorrectly without any warnings or type-checking errors.
Such enum redefinition conflicts are now caught and treated as errors,
so the ``NetControl::DROP`` enums had to be renamed:

* The use as enum of type ``Log::ID`` is renamed to ``NetControl::DROP_LOG``

* The use as enum of type ``NetControl::CatchReleaseInfo`` is renamed to
  ``NetControl::DROP_REQUESTED``

* The use as enum of type ``NetControl::RuleType`` is unchanged and still
  named ``NetControl::DROP``
2020-07-31 16:11:35 -07:00
..
plugins unused variables found via use-def analysis (plus an indentation micro-nit) 2020-04-25 18:06:47 -07:00
__load__.zeek GH-379: move catch-and-release and unified2 scripts to policy/ 2019-06-05 13:33:45 -07:00
cluster.zeek Remove ineffective &default in netcontrol cluster event handler args 2020-04-16 15:40:27 -07:00
drop.zeek GH-1080: Rename conflicting NetControl::DROP enum definitions 2020-07-31 16:11:35 -07:00
main.zeek unused variables found via use-def analysis (plus an indentation micro-nit) 2020-04-25 18:06:47 -07:00
non-cluster.zeek Add warning for ineffective &default arguments in handlers 2020-04-09 22:51:01 -07:00
plugin.zeek GH-379: move catch-and-release and unified2 scripts to policy/ 2019-06-05 13:33:45 -07:00
README More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00
shunt.zeek More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00
types.zeek More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00

The NetControl framework provides a way for Zeek to interact with networking
hard- and software, e.g. for dropping and shunting IP addresses/connections,
etc.