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

StackClash_x86 change bytes for bytearray, interpretation wrong for python 2.6-7 #16

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

11ume
Copy link

@11ume 11ume commented Feb 5, 2018

The new bytes type is 3.x only. The 2.x bytes built-in is just an alias to the str type. There is no new type called bytes in 2.x; Just a new alias and literal syntax for str.

https://github.com/ebranca/owasp-pysec/wiki/Bytes-type-in-python-2-and-python-3

11ume added 2 commits February 5, 2018 20:17
The new bytes type is 3.x only. The 2.x bytes built-in is just an alias to the str type. There is no new type called bytes in 2.x; Just a new alias and literal syntax for str.

https://github.com/ebranca/owasp-pysec/wiki/Bytes-type-in-python-2-and-python-3
Copy link
Owner

@BigNerd95 BigNerd95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you
I'll merge it in next hours

Does this solve some problems? Or it is only a formality?

@11ume
Copy link
Author

11ume commented Feb 7, 2018

if you can ignore this pull request,
the script will work without problems since bytes in py2 is str (),
I thought that the send method of socket, was throwing an expecion but it does,
this don't have a same logic that in python 3 which only wait for a byte object,
the code would, only be badly syntactically.

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 this pull request may close these issues.

2 participants