The private storage mechanisms described in the previous
sections effectively prevent sensitive data resulting from
private computation from being stored in the clear. However,
applications frequently make use of a number of IPC channels during their normal operation. Without any restrictions
in place, private processes might use these channels to
inadvertently leak sensitive data to a public process. If that
public process in turn persists that data, it would circumvent
the protections PRIVEXEC attempts to enforce. Therefore,
PRIVEXEC must also enforce restrictions on IPC to prevent
such scenarios from occurring.