Unsafe Python Library Documentation

unsafe-python A library to assist writing memory-unsafe code in "pure" python, without any imports (i.e. no ctypes etc.) Supports CPython 3.11 and below (3.12 support coming soon?) Note: This is a toy. You probably shouldn't use it for anything serious (or anything at all, really). Core features: addr_of(obj) - A trivial alias of the id() builtin. fakeobj(addr) - Allows for crafting fake heap objects. getmem() - Returns a bytearray view of the current process's virtual memory. setrip(addr) - Sets the RIP register. Argument passing etc. coming soon™. do_rop(payload) - Execute a ROP payload. A trivial example, showing how to dereference a null pointer in pure python. The future is now! >>> import unsafe # (If "no imports" is a requirement, then you can just copy-paste the code) >>> mem = unsafe.getmem() >>> mem[0] Segmentation fault (core dumped) For a less trivial example, check out shellcode_example_nocheats.py, which uses ROP to protect a shellcode buffer, and then jump into it. Why? I don't know. How?

This is a dark-themed documentation page for a fictional Python library that enables memory-unsafe operations in pure Python. It lists absurd low-level features, demonstrates causing a segmentation fault, and answers “Why?” with “I don't know,” while leaving “How?” as the punchline. The meme is used as a reaction to overengineered, dangerous, or inexplicably powerful code presented with casual documentation. EN: This is a dark-themed documentation page for a fictional Python library that enables memory-unsafe operations in pure Python. It lists absurd low-level features, demonstrates causing a segmentation fault, and answers “Why?” with “I don't know,” while leaving “How?” as the punchline. The meme is used as a reaction to overengineered, dangerous, or inexplicably powerful code presented with casual documentation.

• @ithueti / 12815 2024-05-12