Secure Shell (SSH)
Last updated
Prerequisite: The target Linux hosts must be reachable over SSH and accept a single shared credential (password or key). A non-root user works for most fields; serial number and a few privileged details require sudo.
The Linux hosts to scan. Accepts a CIDR (e.g. 192.168.1.0/24), a dashed range (e.g. 192.168.1.10-50), or a comma / newline separated list of IPs and hostnames. Each reachable host becomes one device.
TCP port of the SSH service. (default: 22)
The SSH user used to log in to every target host.
Password for the SSH user. Leave empty if you authenticate with a private key instead.
PEM-formatted SSH private key, used as an alternative to the password. Either a password or a private key must be provided.
Passphrase that decrypts the private key, if it is encrypted.
If checked, privileged commands are run with sudo -n (never prompts) to collect fields such as the system serial number. (default: off)
Seconds to wait for the SSH connection and authentication on each host. Unreachable hosts are skipped after this time. (default: 10)
Seconds to wait for the collection command to return on each host. (default: 30)
Number of hosts scanned in parallel during the sweep. (default: 32)
Maximum number of hosts a single connection may expand to. Larger ranges are rejected to bound the scan. (default: 4096)
Collect the installed package inventory from each host (dpkg / rpm / apk). Adds load per host, so it is off by default. (default: off)
Collect the currently-running systemd services from each host. (default: off)
Attention
Please perform a connection test to ensure there is a valid connection to the Secure Shell (SSH) hosts. When the discovery operation is finalized you will be able to see the details on the Assets page.
Last updated