Previous | Table of Contents | Next |
Security considerations for abstract interfaces are similar to those for regular interfaces
and values (see Section 5.2.9, “Security Considerations,? on page 5-7). This is because
an abstract interface formal parameter type allows either a regular interface (IOR) or a value to be passed. Likewise, an
operation defined in an abstract interface can be implemented by either a regular interface (with “normal? security considerations)
or by a value type (in which case it is a local call, not mediated by the ORB). The security implication of making the choice
between these alternatives a runtime determination is that the programmer must ensure that for both alternatives, no security
violations can
occur. For example, a technique similar to that described in Section 6.5.1, “Passing
Values to Trusted Domains,? on page 6-4 could be used to avoid inadvertently passing
values outside a domain of trust.