Add convenient exploit for _IO_wide_data
#2442
Conversation
|
We should keep a proxy |
|
Oh I see. In case someone use pwntools in library mode right? Should I just write |
|
Since I work on an old branch, should I update my branch with rebase when I'm done and write down the changelog? |
|
How to meet the doctest requirement both in Python 2 and Python 3? |
|
I believe the latest failure is not about bytes' repr, but rather about bytes constructor from array. You can use The documentation should be py3-native (or even py3-only). Back when porting to py3, I implemented a custom doctest comparator for py2 that should accept enough py3 to pass the tests successfully. |
|
So do you mean that I should replace |
|
Are you still planning to work on this feature? |
|
Yes, you know, it's Chinese new year now, I'll do it a few days later. |
|
Yes, don't worry. Happy new year! |
|
Before continue on this giant piece of code, solving some small fixes may be easier. What about #2504 and #2506? Nobody reply to me, and I have no idea about what I need to modify.
|
Merge remote dev to remove annoying Python 2 tests. Update CHANGELOG to stop CHANGELOG test failing.
filepointer: check type and len when setattr; format code and add type hint.
After glibc 2.35, one of exploitable paths is FSOP, utilizing unchecked vtable for
_IO_wide_data. This PR brings related structures in Python and convenient methods to create out-of-box payload.WIP.