at rsteamdeals <| sep |># IT ' S SO BIG <| sep |> It ' s jong ajax <| sep |> That ' s the problem . They can complain all they want . But when you write Jill Stein or the Green Party a check , they are under no obligation to just use it for recounts . <| sep |> Who debunked pizzagate ? <| sep |>. and then it shit on my head . <| sep |> Take the fish . <| sep |> No problem man <| sep |> Particularly when they are diabolically smart , and yes , it can really skew your sense of trust . <| sep |> But it seems that this is usually enabled by default option 2 in your list . Ubuntu does seem to enable this . Note that you can still ptrace your own processes that way but only if the tracing process has indirectly started the traced one . Ubuntu also says that it is ' appropriate for development systems ' to turn it off , which it is . It breaks a lot of development tools which need to ptrace things that are already running or started in a different way . Sometimes you for debugging just need to trace something that was started normally and throwing a debugger inside of the chain ruins it already . But again , the difference is , you make this change once . It ' s not a persistent popup that keeps coming back every time you want to debug something . Upstart itself actually used ptrace by the way as part of its normal function . It needed to know know whether a service it monitored forked or not and used ptrace to get to know that . By default it is not possible for an application to access the memory of another application . Oh no , it still is , it ' s just reduced and ptrace is only one way . The option Ubuntu ships with only allows ptracing if the accessing application started the accessed one in someway and this is only for ptrace , there are many more ways to get an image of a program ' s memory to read it . But ptrace is extra dangerous because it essentially allows you full control of any running process and insert random instructions into it as you please . Also , because Wayland works with file descriptors which point to virtual memory and contain buffers . You can just use proc $ pidof waylandcompositorfd to get a list of the file descriptors and open those regions of virtual memory directly by any other process that runs as the same user . For screen capture it is the compositor that does the enforcement which application can record the screenYeah , but what you suggest is a popup every time something attaches which means you can ' t do it programmatically when you ' re not there at the moment . You can set your kernel to option 3 which limits it to root . And you need root to set it back . But you have to set it back only one , not a popup or some form of confirmation every time something tries to ptrace . If you want to use extra hardcoremode then you are free to disable ptrace protection and use a compositor that enables arbitrary access to the screen . That is up to you . The point is that Wayland gives people an option to not do it . Ehh , no , Wayland doesn ' t give people an option , it ' s just not allowed . X 11 gives people an option with the X 11 SECURITY module where you can disable this kind of stuff if you want to . There are no options regarding this in Wayland at the moment .