Skip to content
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

meterpreter-python: Inconsistent use of tabs and spaces in indentation #265

Closed
jojonas opened this issue Jan 9, 2018 · 6 comments · Fixed by #266
Closed

meterpreter-python: Inconsistent use of tabs and spaces in indentation #265

jojonas opened this issue Jan 9, 2018 · 6 comments · Fixed by #266

Comments

@jojonas
Copy link
Contributor

jojonas commented Jan 9, 2018

As the title indicates, execution of the meterpreter stage fails (tried with Python 3.6.2 on x64 Windows 10).

Traceback (most recent call last):
  File "exploit.py", line 16, in <module>
    exec(d,{'s':s})
  File "<string>", line 645
    try:

I could confirm that in the repository, there is a change in indentation mode between line 644 and 645 of meterpreter.py.

@jojonas
Copy link
Contributor Author

jojonas commented Jan 9, 2018

The culprit seems to be this commit: b5372d2

@busterb
Copy link
Member

busterb commented Jan 9, 2018

Thanks, will take a look.

@busterb
Copy link
Member

busterb commented Jan 9, 2018

@zeroSteiner would you object to us switching python meterpreter to use all spaces as per standard python? In this case my editor always wants to put spaces in python code, which I failed to notice.

@busterb
Copy link
Member

busterb commented Jan 9, 2018

@bwatters-r7 could you please verify that the payload test automation catches the negative case here? Might have to try a newer python with stricter warnings.

@zeroSteiner
Copy link
Contributor

@busterb no, I would not be opposed to that. It's probably better to change it sooner before there are additional extensions and the existing code grows.

@busterb
Copy link
Member

busterb commented Jan 16, 2018

Done, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants