Skip to content
Snippets Groups Projects
Commit 824646d1 authored by pharook's avatar pharook
Browse files

_any_ je interni zalezitost, nepridavejme do uzivatelske dokumentace

parent 078fc14f
No related branches found
No related tags found
No related merge requests found
...@@ -45,7 +45,8 @@ B. Registration ...@@ -45,7 +45,8 @@ B. Registration
* For receiver client: * For receiver client:
- hostname of the machine, where client runs, - hostname of the machine, where client runs,
- client type = receiver, - client type = receiver,
- type of requested events (for example 'portscan', see below) - whether client should receive all events, or type of requested
events (for example 'portscan', see below) otherwise
- receiving of sent events from my organization = yes/no (organizations - receiving of sent events from my organization = yes/no (organizations
are separated based on the top-level and second-level domain), are separated based on the top-level and second-level domain),
- CIDR from which client will communicate with Warden server. - CIDR from which client will communicate with Warden server.
...@@ -138,7 +139,6 @@ D. Types of events ...@@ -138,7 +139,6 @@ D. Types of events
* test - clients can use these at will when debugging/testing, these * test - clients can use these at will when debugging/testing, these
messages will be processed and stored, but ignored later messages will be processed and stored, but ignored later
* other - the rest, uncategorizable yet * other - the rest, uncategorizable yet
* _any_ - clients can use these for receiving of all types of messages
In case of complex scenarios with structured info more events with In case of complex scenarios with structured info more events with
particular parts of information can be created. particular parts of information can be created.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment