From 1abfd8c14864de7b77153a443f15e2434521781a Mon Sep 17 00:00:00 2001 From: "Hahn Axel (hahn)" <axel.hahn@unibe.ch> Date: Mon, 11 Mar 2024 15:38:37 +0100 Subject: [PATCH] update profile readme --- plugins/localdump/profiles/readme.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/plugins/localdump/profiles/readme.md b/plugins/localdump/profiles/readme.md index 0a7f38c..4a7f7a6 100644 --- a/plugins/localdump/profiles/readme.md +++ b/plugins/localdump/profiles/readme.md @@ -21,12 +21,13 @@ To detect the existance of you can use the following keys. If all found detect e | Key | Type | Description | |--- |--- |--- | +| binary | string | Binary that must be found in path. Use comma to separate multiple binaries. | file[] | string | full path of a file. It must match "type". It can be given multiple times. | process | regex | A binary to be matched in the process list -| tcp | integer | A tcp port number that must match -| tcp-process | regex | A process name offering the local tcp port (regex for last column in netstat -tulpen) +| tcp | integer | A tcp port number that must be in use +| tcp-process | regex | A process name offering the local tcp port (regex for last column in `netstat -tulpen`). If process names can differ depending on an os use a pipe to set alternatives eg `postgres|postmaster` | tcp-target | string | A hostname for tcp port check, eg localhost -| type | regex | a matching regex for file -b FILE | grep -i REGEX; see "file[]" +| type | regex | a matching regex for `file -b FILE | grep -i REGEX; see "file[]"` Example: -- GitLab