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.
Hey there,
Not sure if this is within the scope of this project.
Nevertheless the method I made detects whether the underlying driver, which WireShark uses, is running.
I've also taken the liberty to add a method to stop said driver.
Additional information:
When installed, Npcap runs it's driver (
npcap
) automatically on startup, regardless of WireShark running or not.When WireShark runs, it locks the driver therefore attempting to stop the driver directly while WireShark is running will not work. The application must be closed beforehand.
Important considerations:
This method isn't a replacement from proper server-sided api security and rate limiting.
That being said, this method could be used to stop the lowest common denominators from sniffing your api calls.
Improvements:
I could add a method to retrieve the application(s) which are using the npcap driver, to then shut them down one-by-one and finally stop the driver.
I guess I'll wait and see to figure out whether this is in or out of scope.