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

Discussion, Removal of objects when plugins get disabled / removed. #3992

Open
underdarknl opened this issue Dec 30, 2024 · 1 comment
Open

Comments

@underdarknl
Copy link
Contributor

About this feature

Detailed description

When a plugin is removed resulting objects will never be re-checked / can never be invalidated.
All plugins that are part of the proof-chain have this side effect.

Feature benefit/User story

As a user, I want to disable boefjes/nibbles/bits/normalizers and remove or keep the once proven oois.

Specifications

The implementation should include…

  • Allow the user to find objects once proven by a disabled plugin.

  • Allow mass deletion of the proven objects.

  • Disabled boefjes

  • Disabled normalizers

  • Disabled bits

  • Disabled nibbles

  • Deleted report-recipe's?

The same is true for plugins that are no longer available. We should offer this choice as a migration option. (think the removal / move of wappalyzer from a boefje to a normalizer as an example)
The same is also true for newer versions of these plugins, once we get to such a situation.

Additional information

Any additional information, considerations, or context that might be helpful for understanding or evaluating the feature request.

Design

This part should only be filled in by the OpenKAT design team.

Screenshots

Include screenshots of the proposed design changes here.

Figma link

Link to the Figma design for further visualization (if applicable)

Implementation

This part should only be filled in by the developers.

Possible solution

Outline your proposed solution for implementing the feature. You can include any specific ideas, designs, or functionalities here.

Alternatives considered

Describe any alternative approaches or solutions you've considered, and why you believe the proposed solution is superior.

@underdarknl underdarknl added this to KAT Dec 30, 2024
@github-project-automation github-project-automation bot moved this to Incoming features / Need assessment in KAT Dec 30, 2024
@underdarknl underdarknl moved this from Incoming features / Need assessment to To be discussed in KAT Dec 30, 2024
@underdarknl
Copy link
Contributor Author

related:
#230
#323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To be discussed
Development

No branches or pull requests

1 participant