You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merframe reads the memory of the running game through /proc/<pid>/mem.
With kernel.yama.ptrace_scope at 0 or 1, the default of most distributions, this works without any setup.
Proton lets other processes of the same user read it's games/processes.
While untested, a system configured to scope 2 will likely refuse this. Scope 3 will always refuse and can only be lowered by a configuration change and reboot, but if you are on this you will likely have a system admin to complain to.
If Merframe runs into any permission issues, it will be reported as Reading process <pid> is not permitted.
You can check the current scope with:
sysctl kernel.yama.ptrace_scope
Scope 2
You have the following options in case you run into that error at scope 2:
Globally
Globally set your system's memory read scope until the next reboot (will also allow other programs to read memory across processes)
sudo sysctl kernel.yama.ptrace_scope=0
Just for Merframe
Extract the Merframe binary:
./Merframe_amd64.AppImage --appimage-extract
Allow the ptrace capability on the Merframe binary
sudo setcap cap_sys_ptrace=ep ./merframe
You may need to run squashfs-root/AppRun after setting the capability.