Hi,
Do you think it's time to assume that PTRACE_SETOPTIONS and
PTRACE_O_TRACESYSGOOD|PTRACE_O_TRACEEXEC|PTRACE_O_TRACECLONE are
universally available and working?
If yes, then all code that supports post-execve SIGTRAP and implements
fork/vfork/clone->CLONE_PTRACE substitution could be removed.
On 15 Feb 2015 15:47, Dmitry V. Levin wrote:
> Do you think it's time to assume that PTRACE_SETOPTIONS and
> PTRACE_O_TRACESYSGOOD|PTRACE_O_TRACEEXEC|PTRACE_O_TRACECLONE are
> universally available and working?
>
> If yes, then all code that supports post-execve SIGTRAP and implements
> fork/vfork
On Sun, Feb 15, 2015 at 9:49 AM, Mike Frysinger wrote:
> On 15 Feb 2015 15:47, Dmitry V. Levin wrote:
>> Do you think it's time to assume that PTRACE_SETOPTIONS and
>> PTRACE_O_TRACESYSGOOD|PTRACE_O_TRACEEXEC|PTRACE_O_TRACECLONE are
>> universally available and working?
>>
>> If yes, then all code
Android's been >= 2.6 forever so we won't notice.
On Sun, Feb 15, 2015 at 10:48 AM, Philippe Ombredanne
wrote:
> On Sun, Feb 15, 2015 at 9:49 AM, Mike Frysinger wrote:
>> On 15 Feb 2015 15:47, Dmitry V. Levin wrote:
>>> Do you think it's time to assume that PTRACE_SETOPTIONS and
>>> PTRACE_O_TRA
