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

Fix: Fix modify config preference, set pref_... fields in cleanup-config-prefs #2150

Merged
merged 2 commits into from
Mar 11, 2024

Conversation

timopollmeier
Copy link
Member

What

When modifying a config, the database fields containing the
VT id, preference id, type and name are now set for all types.

The --optimize option cleanup-config-prefs now also sets the fields
pref_nvt, pref_id, pref_type, pref_name if they are missing or invalid
for VT preferences or sets them to NULL for scanner preferences.

Why

This fixes the preferences not working correctly after modifying them.

References

GEA-450

@timopollmeier timopollmeier requested a review from a team as a code owner March 11, 2024 11:02
Copy link

Conventional Commits Report

Type Number
Bug Fixes 2

🚀 Conventional commits found.

When modifying a config, the database fields containing the
VT id, preference id, type and name are now set for all types.

This fixes the preferences not working correctly after modifying them.
The --optimize option cleanup-config-prefs now also sets the fields
pref_nvt, pref_id, pref_type, pref_name if they are missing or invalid
for VT preferences or sets them to NULL for scanner preferences.
@a-h-abdelsalam a-h-abdelsalam force-pushed the fix-modify-config-preference branch from ff81467 to 097a880 Compare March 11, 2024 15:14
@a-h-abdelsalam a-h-abdelsalam merged commit 54a0645 into main Mar 11, 2024
9 checks passed
@a-h-abdelsalam a-h-abdelsalam deleted the fix-modify-config-preference branch March 11, 2024 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants