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.
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 python meterpreter network method exceptions for OSX #651
Fix python meterpreter network method exceptions for OSX #651
Changes from 1 commit
c494d9e
a1166ac
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer pytest, but I thought only depending on the inbuilt testing library would be easier for contributors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OSX was returning the integer flag value here, whilst linux was returning the string flag names. Now the implementations return both separately
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be introducing new data into the TLV, is there value for both vs just shifting to a more consistent type retuned in
flags
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TLV_TYPE_INTERFACE_FLAGS
has always been a string:Previously the OSX code path was was extracting out the integer value for flags instead of a string like in the Linux codepath, i.e. in the osx code path attempted to write out
8836
instead of"UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST"
from the below ifconfig outputThis is now updated to send the string flag names for both OSX and Linux
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it,
stdapi_net_config_get_interfaces_via_netlink
was returningflags
as a set of strings names andstdapi_net_config_get_interfaces_via_osx_ifconfig
was returningflags
as numeric values nowNow both return
flags
as numeric values andflags_str
as string names and onlyflags_str
is being placed in the response as aTLV_TYPE_INTERFACE_FLAGS
packet.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Required in newer versions of Python - when the later code attempts to split this result with
for line in output.split('\n')
the following exception is raised:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's a file descriptor leak here, will put up a separate PR for this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixes:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll skip verifying the exact bytes for now, this was just an MVP "make sure it doesn't explode" test for now