- Push much of the logic for p_cansignal() behind cr_cansignal, which   authorized based on a subject credential rather than a subject process.   This will permit the same logic to be reused in situations where only   the credential generating the signal is available, such as in the   delivery of SIGIO. - Because of two clauses, the automatic success against curproc,   and the session semantics for SIGCONT, not all logic can be pushed   into cr_cansignal(), but those cases should not apply for most other   consumers of cr_cansignal(). - This brings the base system inter-process authorization code more   into line with the MAC implementation.
- Push much of the logic for p_cansignal() behind cr_cansignal, which
  authorized based on a subject credential rather than a subject process.
  This will permit the same logic to be reused in situations where only
  the credential generating the signal is available, such as in the
  delivery of SIGIO.
- Because of two clauses, the automatic success against curproc,
  and the session semantics for SIGCONT, not all logic can be pushed
  into cr_cansignal(), but those cases should not apply for most other
  consumers of cr_cansignal().
- This brings the base system inter-process authorization code more
  into line with the MAC implementation.

Obtained from:	TrustedBSD Project
Sponsored by:	DARPA, NAI Labs

jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase