Update gvm-portnames-update #802
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
mattmundell
requested changes
Oct 16, 2019
bjoernricks
previously approved these changes
Oct 16, 2019
mattmundell
approved these changes
Oct 21, 2019
mcjon3z
added a commit
to isaudits/docker-gvm
that referenced
this pull request
Apr 8, 2020
… into release to work)
|
Seems this was never backported to the gvm-9.0 branch, did this in #1166 |
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.
When issueing the command
gvm-portnames-update service-names-port-numbers.xmlto update iana service names we get:
Simple name change (openvassd -> openvas). Openvassd was the scanner's name in previous versions of gvm.
Checklist: