You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if class NodeTrackingInformation is not indicating the right occurrence time of the last attack?
The time() func at line 248 and 671 in actions.py would set the nodes's last_reimaging_time and last_owned time to be '00:00:00'. So when the cyber attacker attempts to re-connect to a conquered but lately reimaged node, func __is_node_owned_history at line 483 would recognize the reimaged node as a currently owned node. Therefore the cyber attacker can never connect to a reimaged node successfully.
Is it true, or am I mistaking something here😂?
The text was updated successfully, but these errors were encountered:
TTDietCoke
changed the title
Something wrong with defender's REIMAGE func?
Something wrong with the node's last owned time and last reimaged time?
Dec 6, 2022
Thanks for reporting. That's a bug where the action.py file imports the timemodule with from datetime import time instead of importing the time function using from time import time. Testing a fix, will submit a PR soon
Sorry to bother.
I am wondering if class NodeTrackingInformation is not indicating the right occurrence time of the last attack?
The time() func at line 248 and 671 in actions.py would set the nodes's last_reimaging_time and last_owned time to be '00:00:00'. So when the cyber attacker attempts to re-connect to a conquered but lately reimaged node, func __is_node_owned_history at line 483 would recognize the reimaged node as a currently owned node. Therefore the cyber attacker can never connect to a reimaged node successfully.
Is it true, or am I mistaking something here😂?
The text was updated successfully, but these errors were encountered: