+ The client uses the delete_alert command to delete an existing + alert. +
++ Since this is a destructive command, the client is advised to ask + for confirmation from the user before sending this command to the + Manager. +
+- The client uses the delete_alert command to delete an existing - alert. -
-- Since this is a destructive command, the client is advised to ask - for confirmation from the user before sending this command to the - Manager. -
-- The client uses the delete_report command to delete an existing report. + The client uses the delete_permission command to delete an existing permission.
Since this is a destructive command, the client is advised to ask @@ -6462,10 +6462,16 @@ END:VCALENDAR
- The client uses the delete_permission command to delete an existing permission. + The client uses the delete_port_list command to delete an existing + port list.
Since this is a destructive command, the client is advised to ask @@ -6507,7 +6514,7 @@ END:VCALENDAR
- The client uses the delete_port_list command to delete an existing - port list. + The client uses the delete_port_range command to delete an existing + port range.
Since this is a destructive command, the client is advised to ask @@ -6559,16 +6566,10 @@ END:VCALENDAR
- The client uses the delete_port_range command to delete an existing - port range. + The client uses the delete_report command to delete an existing report.
Since this is a destructive command, the client is advised to ask @@ -6611,7 +6611,7 @@ END:VCALENDAR
+ The client uses the get_aggregate command to get aggregated data like + counts or averages of various resources. +
++ Unlike other get_... commands, get_aggregates ignores the filter + keywords "first" and "rows". It also does not support selecting single + items by id or getting items from the trashcan. +
- The client uses the get_aggregate command to get aggregated data like - counts or averages of various resources. -
-- Unlike other get_... commands, get_aggregates ignores the filter - keywords "first" and "rows". It also does not support selecting single - items by id or getting items from the trashcan. -
+ The client uses the get_alerts command to get alert information. + If the command sent by the client was valid, the manager will + reply with a list of alerts to the client.+ The client uses the get_license command to get the current license. +
++ This command is only available if gvmd is built with the licensing + library (libtheia). +
- The client uses the get_license command to get the current license. -
-- This command is only available if gvmd is built with the licensing - library (libtheia). -
-- The client uses the get_nvts command to get NVT information. -
- -- This command may always include a details flag, a config, a sort - order and a sort field. If the command includes a details flag, the - manager also consults the timeout, preference_count and preferences - flags. -
-- The NVT OID, family name and config attributes limit the listing to - a single NVT or all NVTs in a particular family and/or config. -
-- If the details flag is present the manager will send full details - of the NVT, otherwise it will send just the NVT name. -
-- With the preferences flag the manager includes in the listing, the - values of each listed NVT's preferences for the given config. The - timeout flag does the same for the special timeout preference. - If the config contains no values for a preference, the default value - of the preference is returned. The same applies if no config is given. -
-- If the manager possesses an NVT collection, it will reply with the - NVT information. If the manager cannot access a list of available - NVTs at that time, it will reply with the 503 response. -
-- NVT categories: 0 init, 1 scanner, 2 settings, 3 infos, 4 attack, 5 mixed, - 6 destructive attack, 7 denial, 8 kill host, 9 flood, 10 end, and 11 unknown. -
+ The client uses the get_notes command to get note information. + If the command sent by the client was valid, the manager will + reply with a list of notes to the client.+ The client uses the get_nvts command to get NVT information. +
+ ++ This command may always include a details flag, a config, a sort + order and a sort field. If the command includes a details flag, the + manager also consults the timeout, preference_count and preferences + flags. +
++ The NVT OID, family name and config attributes limit the listing to + a single NVT or all NVTs in a particular family and/or config. +
++ If the details flag is present the manager will send full details + of the NVT, otherwise it will send just the NVT name. +
++ With the preferences flag the manager includes in the listing, the + values of each listed NVT's preferences for the given config. The + timeout flag does the same for the special timeout preference. + If the config contains no values for a preference, the default value + of the preference is returned. The same applies if no config is given. +
++ If the manager possesses an NVT collection, it will reply with the + NVT information. If the manager cannot access a list of available + NVTs at that time, it will reply with the 503 response. +
++ NVT categories: 0 init, 1 scanner, 2 settings, 3 infos, 4 attack, 5 mixed, + 6 destructive attack, 7 denial, 8 kill host, 9 flood, 10 end, and 11 unknown. +
- The client uses the get_port_lists command to get port list - information. -
-- The client uses the get_preferences command to get preference information. - If the command sent by the client was valid, the manager will reply with - a list of preferences to the client. If the manager cannot access a list - of available NVTs at present, it will reply with the 503 response. -
-- When the command includes a config_id attribute, the preference element - includes the preference name, type and value, and the NVT to which the - preference applies. Otherwise, the preference element includes just the - name and value, with the NVT and type built into the name. + The client uses the get_port_lists command to get port list + information.
- The client uses the get_reports command to get report information. -
-- The XML report format is sent as XML. All other formats are sent in - Base64 encoding. -
-- The "lean" attribute requests a reduced report. This option is - specifically to support GSA performance when loading big reports, so - the effect of "lean" may change between versions, even between minor - versions. -
-- Currently "lean" skips certain result elements (MODIFICATION_TIME, - SCAN_NVT_VERSION, THREAT, ORIGINAL_THREAT), skips SOURCE/TYPE of host - details, skips certain host details ("EXIT_CODE" when equal to - "EXIT_NONVULN", "scanned_with_scanner", "scanned_with_feedtype", - "scanned_with_feedversion", "OS" and "traceroute"), skips certain - elements when they are empty (REFS, QOD/TYPE, ...), and skips - ORIGINAL_SEVERITY when it is the same as SEVERITY. -
-- "lean" will always work with the XML report format, but will not - necessarily work with any others. -
-- In this case the response is empty, and simply indicates success - via the status code. -
-- The client uses the get_report_formats command to get report format - information. + The client uses the get_preferences command to get preference information. + If the command sent by the client was valid, the manager will reply with + a list of preferences to the client. If the manager cannot access a list + of available NVTs at present, it will reply with the 503 response. +
++ When the command includes a config_id attribute, the preference element + includes the preference name, type and value, and the NVT to which the + preference applies. Otherwise, the preference element includes just the + name and value, with the NVT and type built into the name.
+ The client uses the get_report_formats command to get report format + information. +
++ The client uses the get_reports command to get report information. +
++ The XML report format is sent as XML. All other formats are sent in + Base64 encoding. +
++ The "lean" attribute requests a reduced report. This option is + specifically to support GSA performance when loading big reports, so + the effect of "lean" may change between versions, even between minor + versions. +
++ Currently "lean" skips certain result elements (MODIFICATION_TIME, + SCAN_NVT_VERSION, THREAT, ORIGINAL_THREAT), skips SOURCE/TYPE of host + details, skips certain host details ("EXIT_CODE" when equal to + "EXIT_NONVULN", "scanned_with_scanner", "scanned_with_feedtype", + "scanned_with_feedversion", "OS" and "traceroute"), skips certain + elements when they are empty (REFS, QOD/TYPE, ...), and skips + ORIGINAL_SEVERITY when it is the same as SEVERITY. +
++ "lean" will always work with the XML report format, but will not + necessarily work with any others. +
++ In this case the response is empty, and simply indicates success + via the status code. +
+- The client uses the "get_users" command to retrieve the list of user - accounts on the Scanner. + The client uses the "get_tls_certificates" command to retrieve one + or more TLS certificates.
- The client uses the "get_tls_certificates" command to retrieve one - or more TLS certificates. + The client uses the "get_users" command to retrieve the list of user + accounts on the Scanner.
+ The client uses the modify_tag command to change an existing tag. +
+- The client uses the modify_tag command to change an existing tag. -
-