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 sending prefs for whole, growing VT families #1603

Merged
merged 5 commits into from
Jul 6, 2021

Conversation

timopollmeier
Copy link
Member

@timopollmeier timopollmeier commented Jun 30, 2021

What:
If a VT family is growing and all VTs are selected, vt_single elements
are used instead of a vt_group one again so preferences can be set for
the VTs.

Why:
The preferences were not sent for VTs where the whole family was selected.

How did you test it:
By running a scan with a config where the preference "Disable brute force checks" of NVT "Options for Brute Force NVTs" (1.3.6.1.4.1.25623.1.0.103697) in the Settings family was set to "yes" and monitoring Redis whether the preference appears with sudo redis-cli -s /run/redis-openvas/redis.sock monitor > /tmp/redis.log

Checklist:

If a VT family is growing and all VTs are selected, vt_single elements
are used instead of a vt_group one again so preferences can be set for
the VTs.
@timopollmeier timopollmeier requested a review from a team as a code owner June 30, 2021 15:34
@timopollmeier timopollmeier added the backport-to-stable This pull request will be backported to the stable branch label Jun 30, 2021
@bjoernricks bjoernricks merged commit 1e8611b into greenbone:master Jul 6, 2021
sarahd93 added a commit that referenced this pull request Jul 6, 2021
Fix sending prefs for whole, growing VT families (backport #1603)
@timopollmeier timopollmeier deleted the revert-vt_groups-use branch October 15, 2021 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-stable This pull request will be backported to the stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants