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 know that duplicate files will not be scanned again, but can it not affect my project, can the scan records be displayed normally, and can a feature be added to force rescanning, because the vulnerability library is also being updated, and other plugins are also being updated. Rescanning through interfaces is also a scenario. Where can I modify the code to achieve this
Steps to reproduce
1
Observed Behavior
1
Expeced Behavior
1
Installation logs
install.log
PASTE HERE
Backend logs
fact_main_backend.log
PASTE HERE
Frontend logs
fact_main_frontend.log
PASTE HERE
Other information
No response
The text was updated successfully, but these errors were encountered:
Hi, I'm not sure if I understand correctly what you want. Do you want to update the analysis of a specific plugin for a whole firmware image that you uploaded to FACT?
You can update an existing analysis by clicking on the "Update analysis" button on the analysis page. You then need to select which analysis plugins to run. This will only run the analysis if the version of the plugin changed or if the analysis is missing.
You can also redo the whole unpacking and analysis with the "Redo analysis" button on the analysis page of the firmware image. Caution: this deletes everything from the database and unpacks and analyzes the firmware image as if it was newly uploaded.
You can also trigger an update using REST as documented here.
FACT version
4.3
Environment
I know that duplicate files will not be scanned again, but can it not affect my project, can the scan records be displayed normally, and can a feature be added to force rescanning, because the vulnerability library is also being updated, and other plugins are also being updated. Rescanning through interfaces is also a scenario. Where can I modify the code to achieve this
Steps to reproduce
1
Observed Behavior
1
Expeced Behavior
1
Installation logs
install.log
Backend logs
fact_main_backend.log
Frontend logs
fact_main_frontend.log
Other information
No response
The text was updated successfully, but these errors were encountered: