Update known Vendor IDs after /0 scan #18
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
This includes new Vendor IDs seen during a UDP/500 scan against /0 using Nmap's probe (a lot more Vendor IDs are yet to be identified). For strongSwan / Openswan / FreeS/WAN / Libreswan, hash "bruteforces" have been performed based on quick source code readings.
|
Any chance you could merge this one one day, @royhills? Is there something else I need to do? Thanks! |
|
Apologies for the delay. I'd missed this because travis was flagging it as not building, which is obviously false as it's not a code change. I'll deal with any travis issues later. Many thanks for taking the time to do this. If a /0 scan mean what I think it does: scanning the whole IPv4 address space, then it must have taken quite a bit of time. |
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.
This includes new Vendor IDs seen during a UDP/500 scan against /0
using Nmap's probe (a lot more Vendor IDs are yet to be identified).
For strongSwan / Openswan / FreeS/WAN / Libreswan, hash "bruteforces"
have been performed based on quick source code readings.