Change NVT prefs format #275
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kroosec
requested review from
ArnoStiefvater,
mattmundell,
timopollmeier and
a team
kroosec
force-pushed
the
nvt-pref-name
branch
from
99369a2
to
d70fd77
Compare
|
@cfi-gb Added the check in script_add_preference() to see if a preference with the same name exists already. |
2 tasks
timopollmeier
approved these changes
Feb 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Send and receive NVT preferences in OID:PrefType:PrefName instead of NVTName[PrefType]:PrefName.
This allows NVT plugins to change their names without breaking existing scan configs.
Relevant gvmd PR greenbone/gvmd#394