Move the crypto code into the Python Meterpreter - #775
Merged
Conversation
zeroSteiner
changed the title
zeroSteiner
marked this pull request as ready for review
October 6, 2025 21:32
This ensures that the crypto functionality is present without needing to be patched in by framework. It also means that line numbers are correct in the debugging output.
dledda-r7
force-pushed
the
fix/met/py-embed-crypto
branch
from
October 7, 2025 19:38
b185229 to
cc628e0
Compare
Contributor
python 2.6python 2.7python 3.1python 3.13.7 |
smcintyre-r7
pushed a commit
that referenced
this pull request
Jul 6, 2026
Move the crypto code into the Python Meterpreter
smcintyre-r7
pushed a commit
that referenced
this pull request
Jul 7, 2026
Move the crypto code into the Python Meterpreter
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.
This ensures that the crypto functionality is present without needing to be patched in by framework. This should also ensure that line numbers are correct for uncaught stack traces that occur early in the init process because multiple lines are no longer being patched in.
Once this is in place, the Framework side of things can have its code removed because it'll all live here in the payloads directory.
Testing
Test that a session can be initialized with each of the supported Python versions:
Python 2.5(skip this, Python 2.5 is broken but it's not due to the changes here)