[MS.Docs]:ReadProcessMemory 函数状态:
如果函数失败,则返回值为 0(零)。要获取扩展的错误信息,请调用GetLastError。
这是一个小例子。
代码00.py:
#!/usr/bin/env python
import sys
import ctypes as ct
from ctypes import wintypes as wt
PROCESS_VM_READ = 0x0010
def main(*argv):
kernel32 = ct.WinDLL("kernel32")
OpenProcess = kernel32.OpenProcess
OpenProcess.argtypes = [wt.DWORD, wt.BOOL, wt.DWORD]
OpenProcess.restype = wt.HANDLE
ReadProcessMemory = kernel32.ReadProcessMemory
ReadProcessMemory.argtypes = [wt.HANDLE, wt.LPCVOID, wt.LPVOID, ct.c_size_t, ct.POINTER(ct.c_size_t)]
ReadProcessMemory.restype = wt.BOOL
GetLastError = kernel32.GetLastError
GetLastError.argtypes = []
GetLastError.restype = wt.DWORD
CloseHandle = kernel32.CloseHandle
CloseHandle.argtypes = [wt.HANDLE]
CloseHandle.restype = wt.BOOL
np_pid = 34376 # Got it from a process monitoring tool
np = OpenProcess(PROCESS_VM_READ, 0, np_pid)
if not np:
print("OpenProcess failed: {0:d}".format(GetLastError()))
return
buf_len = 0x0F # 0xFF # Lower value for display purposes
buf = ct.create_string_buffer(buf_len)
read = ct.c_size_t()
addr = 0x00001CF26F20000 # Got a readable address from VMMap as well, but I don't know the one where the actual text is stored
res = ReadProcessMemory(np, addr, buf, buf_len, ct.byref(read))
if res:
print("Read ({0:d} bytes) from process ({1:d}) address 0x{2:016X}:".format(read.value, np_pid, addr))
text = ""
for i in range(read.value):
text += " 0x{0:02X}".format(ord(buf[i]))
print(text)
else:
print("ReadProcessMemory failed: {0:d}".format(GetLastError()))
CloseHandle(np)
if __name__ == "__main__":
print("Python {0:s} {1:d}bit on {2:s}\n".format(" ".join(elem.strip() for elem in sys.version.split("\n")), 64 if sys.maxsize > 0x100000000 else 32, sys.platform))
main(*sys.argv[1:])
print("\nDone.")
输出:
[cfati@CFATI-5510-0:e:\Work\Dev\StackOverflow\q063273381]> "e:\Work\Dev\VEnvs\py_pc064_03.07.06_test0\Scripts\python.exe" code00.py
Python 3.7.6 (tags/v3.7.6:43364a7ae0, Dec 19 2019, 00:42:30) [MSC v.1916 64 bit (AMD64)] 64bit on win32
Read (15 bytes) from process (34376) address 0x000001CF26F20000:
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xC2 0x3B 0x78 0x62 0xE6 0xFA 0x00
Done.
更新#0
我不知道记事本如何在内部组织它的内存。我可以假设文本存储在一个缓冲区(或者更多,可能是每行一个,...)中,该缓冲区应该驻留在堆区域中。但具体在哪里我不能说。您可以使用工具检查进程内存(我知道CheatEngine可以做到这一点)在内存内容和文本之间进行匹配,并获取该地址,并将其粘贴到代码中,但我认为这会:
- 击败脚本的目的(因为脚本用于自动化,代替用户完成工作)
- 不靠谱。缓冲区分配有特定长度。如果用户继续在记事本中输入内容,最终该缓冲区将变满并且(在幕后)它将被重新定位,这将(很可能)更改其地址
总而言之,我不认为这是要走的路。您可以搜索替代方案,例如使用WinAPI将消息(可能是WM_GETTEXT)发送到记事本窗口以获取文本。我不知道该怎么做,但我记得我能够使用WM_CHAR以编程方式在记事本中插入字符。或者您可以发送一个, ,然后获取剪贴板内容。
Ctrl + ACtrl + C