Ticket #139 (new test)

Opened 6 months ago

Fingerprint Consistency Verification

Reported by: kindlund Assigned to: mbriggs
Priority: low Milestone: 1.1
Component: Drone Version: none
Severity: none Keywords: drone, fingerprints, schema, database
Cc:

Description

When a cloned VM's integrity check fails, the Manager should have properly inserted a fingerprint into the database. If possible, a very useful unit test would be to walk the database and verify that each client that has a status 'suspicious' and 'compromised' should have one (and only one) fingerprint associated with it.

Attachments

Add/Change #139 (Fingerprint Consistency Verification)




Change Properties
Action