Allow pdptrace(2) and pdopenpid(2) in capability mode

[kib]

Summary

kern: add p_canopen()

The function defines the policy for allowing to open a pid.


pdptrace(2): allow debugging in capability mode

The pdopenpid(2) and pdptrace(2) syscalls are allowed in capability
mode.  Add the chicken switch security.bsd.ptrace_in_cap_mode, which
disables them without reboot, if needed.

For ptrace(2), the PT_ATTACH by pid request is unconditionally disabled
in the cap mode.  All other requests are enabled, but that would only
work if we already have the process reparented to the caller as the
debugger.  The ptrace(PT_ATTACH | PT_PROCDESC) call is allowed,

The descriptor passed to PT_ATTACH must have the CAP_PTRACE
capability enabled. This capability is not enabled by default by
pdfork()/pdopenpid(), and the calls do not return a procdesc suitable
for debugging. The opening code must prepare for debugging in advance by
passing the PD_PTRACE_CAP flag to pdfork()/pdopenpid().

In addition, the pdopenpid() is allowed to open processes which are
either direct children of the caller, or are debuggees already
attached to the calling process.  This is reasonable because we
could have controlled the child on fork anyway.

The procdesc-less debuggee can legitimately appear due to ptrace
FOLLOW-FORK mode.

For ptrace(2), allow PT_CONTINUE and PT_GET_CHILDREN for current process in cap mode as well.

ptrace.2/pdfork.2: document PD_PTRACE_CAP, and ptrace(2) in cap mode

[kib]

Adjust to pdptrace(2) instead of PT_PROCDESC.