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
It would be neat to show the changes over time rather than the end state. For example, if you run one scan per day, np would start at the oldest and process scan 1:
$ np
2022-01-01 12:10 AM 10.1.23.5 80/tcp open
2022-01-01 12:10 AM 10.1.23.5 22/tcp open
Then a subsequent scan against the host after SNMP has been enabled:
2022-01-02 12:10 AM 10.1.23.5 161/udp open
And later HTTP is disabled:
2022-01-03 12:10 AM 10.1.23.5 80/tcp closed
This would allow us to review only the changes for each new scan processed.
The text was updated successfully, but these errors were encountered:
This gets a bit thorny based on where we can detect a change (when parsing the scan) and when we surface that to the user (result printing). I wonder if it would be sufficient to do a diff <(np -path scans -exclude newfile.xml) <(np -path newfile.xml)?
It would be neat to show the changes over time rather than the end state. For example, if you run one scan per day,
np
would start at the oldest and process scan 1:Then a subsequent scan against the host after SNMP has been enabled:
And later HTTP is disabled:
This would allow us to review only the changes for each new scan processed.
The text was updated successfully, but these errors were encountered: