Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I uploaded duplicate files to create a project, but failed #1329

Open
chenjianquan7 opened this issue Jan 17, 2025 · 1 comment
Open

I uploaded duplicate files to create a project, but failed #1329

chenjianquan7 opened this issue Jan 17, 2025 · 1 comment
Labels

Comments

@chenjianquan7
Copy link

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
PASTE HERE

Backend logs

fact_main_backend.log
PASTE HERE

Frontend logs

fact_main_frontend.log
PASTE HERE

Other information

No response

@jstucke
Copy link
Collaborator

jstucke commented Jan 17, 2025

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.

Image

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.

Image

You can also trigger an update using REST as documented here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants