![]() ![]() Neither are considered unique (think DHCP). The reason for this is in the case of a discovered device that we don't have credentials for, we have virtually no information except the IP and maybe the DNS Hostname. Match the Google Cloud ID (not configurable).Īs at Open-AudIT 3.3.0 we will be implementing a match routine that essentially says "If all I have is an IP, and that IP belongs to a device in the database and that device has not been audited, match that device regardless of the match_ip rule.Match the Opmantek UUID (not configurable). ![]() Matching is conducted in the following order: The logic for device matching is contained in the m_devices.php file, which on a Linux install can be found here: /usr/local/open-audit/code_igniter/application/models/ There is a good article linked here that details the why's of hardware IDs. To retrieve the UUID (from the motherboard), we need to run dmidecode, which does require root. Unfortunately, when you clone an ESXi guest, the Dbus ID does not get recreated - hence our concatenating this with the hostname. We can also use other options as per the below table, but we can retrieve the Dbus ID without root. When matching a Linux based device, we prefer to use the Dbus id concatenated with the hostname. ![]()
0 Comments
Leave a Reply. |