fix: follow symlink for libs on ssh connection#2338
Merged
peace-maker merged 1 commit intoGallopsled:devfrom Jan 22, 2024
Merged
fix: follow symlink for libs on ssh connection#2338peace-maker merged 1 commit intoGallopsled:devfrom
peace-maker merged 1 commit intoGallopsled:devfrom
Conversation
peace-maker
approved these changes
Jan 22, 2024
Member
|
Thank you! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pwntools Pull Request
When running a process over SSH, if the lib used is a symlink, then the addresses returned are wrong. This is because we get the address from
/proc/PID/mapsbut we use the symlink lib name, and not the "real" lib name.I corrected it by using
readlink -fwhich return the actual lib used.Changelog
Since it's a really small change, should I still push a change to the Changelog?