cannam@134: // Copyright (c) 2015 Sandstorm Development Group, Inc. and contributors cannam@134: // Licensed under the MIT License: cannam@134: // cannam@134: // Permission is hereby granted, free of charge, to any person obtaining a copy cannam@134: // of this software and associated documentation files (the "Software"), to deal cannam@134: // in the Software without restriction, including without limitation the rights cannam@134: // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell cannam@134: // copies of the Software, and to permit persons to whom the Software is cannam@134: // furnished to do so, subject to the following conditions: cannam@134: // cannam@134: // The above copyright notice and this permission notice shall be included in cannam@134: // all copies or substantial portions of the Software. cannam@134: // cannam@134: // THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR cannam@134: // IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, cannam@134: // FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE cannam@134: // AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER cannam@134: // LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, cannam@134: // OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN cannam@134: // THE SOFTWARE. cannam@134: cannam@134: #ifndef CAPNP_MEMBRANE_H_ cannam@134: #define CAPNP_MEMBRANE_H_ cannam@134: // In capability theory, a "membrane" is a wrapper around a capability which (usually) forwards cannam@134: // calls but recursively wraps capabilities in those calls in the same membrane. The purpose of a cannam@134: // membrane is to enforce a barrier between two capabilities that cannot be bypassed by merely cannam@134: // introducing new objects. cannam@134: // cannam@134: // The most common use case for a membrane is revocation: Say Alice wants to give Bob a capability cannam@134: // to access Carol, but wants to be able to revoke this capability later. Alice can accomplish this cannam@134: // by wrapping Carol in a revokable wrapper which passes through calls until such a time as Alice cannam@134: // indicates it should be revoked, after which all calls through the wrapper will throw exceptions. cannam@134: // However, a naive wrapper approach has a problem: if Bob makes a call to Carol and sends a new cannam@134: // capability in that call, or if Carol returns a capability to Bob in the response to a call, then cannam@134: // the two are now able to communicate using this new capability, which Alice cannot revoke. In cannam@134: // order to avoid this problem, Alice must use not just a wrapper but a "membrane", which cannam@134: // recursively wraps all objects that pass through it in either direction. Thus, all connections cannam@134: // formed between Bob and Carol (originating from Alice's original introduction) can be revoked cannam@134: // together by revoking the membrane. cannam@134: // cannam@134: // Note that when a capability is passed into a membrane and then passed back out, the result is cannam@134: // the original capability, not a double-membraned capability. This means that in our revocation cannam@134: // example, if Bob uses his capability to Carol to obtain another capability from her, then send cannam@134: // it back to her, the capability Carol receives back will NOT be revoked when Bob's access to cannam@134: // Carol is revoked. Thus Bob can create long-term irrevocable connections. In most practical use cannam@134: // cases, this is what you want. APIs commonly rely on the fact that a capability obtained and then cannam@134: // passed back can be recognized as the original capability. cannam@134: // cannam@134: // Mark Miller on membranes: http://www.eros-os.org/pipermail/e-lang/2003-January/008434.html cannam@134: cannam@134: #include "capability.h" cannam@134: cannam@134: namespace capnp { cannam@134: cannam@134: class MembranePolicy { cannam@134: // Applications may implement this interface to define a membrane policy, which allows some cannam@134: // calls crossing the membrane to be blocked or redirected. cannam@134: cannam@134: public: cannam@134: virtual kj::Maybe inboundCall( cannam@134: uint64_t interfaceId, uint16_t methodId, Capability::Client target) = 0; cannam@134: // Given an inbound call (a call originating "outside" the membrane destined for an object cannam@134: // "inside" the membrane), decides what to do with it. The policy may: cannam@134: // cannam@134: // - Return null to indicate that the call should proceed to the destination. All capabilities cannam@134: // in the parameters or result will be properly wrapped in the same membrane. cannam@134: // - Return a capability to have the call redirected to that capability. Note that the redirect cannam@134: // capability will be treated as outside the membrane, so the params and results will not be cannam@134: // auto-wrapped; however, the callee can easily wrap the returned capability in the membrane cannam@134: // itself before returning to achieve this effect. cannam@134: // - Throw an exception to cause the call to fail with that exception. cannam@134: // cannam@134: // `target` is the underlying capability (*inside* the membrane) for which the call is destined. cannam@134: // Generally, the only way you should use `target` is to wrap it in some capability which you cannam@134: // return as a redirect. The redirect capability may modify the call in some way and send it to cannam@134: // `target`. Be careful to use `copyIntoMembrane()` and `copyOutOfMembrane()` as appropriate when cannam@134: // copying parameters or results across the membrane. cannam@134: // cannam@134: // Note that since `target` is inside the capability, if you were to directly return it (rather cannam@134: // than return null), the effect would be that the membrane would be broken: the call would cannam@134: // proceed directly and any new capabilities introduced through it would not be membraned. You cannam@134: // generally should not do that. cannam@134: cannam@134: virtual kj::Maybe outboundCall( cannam@134: uint64_t interfaceId, uint16_t methodId, Capability::Client target) = 0; cannam@134: // Like `inboundCall()`, but applies to calls originating *inside* the membrane and terminating cannam@134: // outside. cannam@134: // cannam@134: // Note: It is strongly recommended that `outboundCall()` returns null in exactly the same cases cannam@134: // that `inboundCall()` return null. Conversely, for any case where `inboundCall()` would cannam@134: // redirect or throw, `outboundCall()` should also redirect or throw. Otherwise, you can run cannam@134: // into inconsistent behavion when a promise is returned across a membrane, and that promise cannam@134: // later resolves to a capability on the other side of the membrane: calls on the promise cannam@134: // will enter and then exit the membrane, but calls on the eventual resolution will not cross cannam@134: // the membrane at all, so it is important that these two cases behave the same. cannam@134: cannam@134: virtual kj::Own addRef() = 0; cannam@134: // Return a new owned pointer to the same policy. cannam@134: // cannam@134: // Typically an implementation of MembranePolicy should also inherit kj::Refcounted and implement cannam@134: // `addRef()` as `return kj::addRef(*this);`. cannam@134: // cannam@134: // Note that the membraning system considers two membranes created with the same MembranePolicy cannam@134: // object actually to be the *same* membrane. This is relevant when an object passes into the cannam@134: // membrane and then back out (or out and then back in): instead of double-wrapping the object, cannam@134: // the wrapping will be removed. cannam@134: }; cannam@134: cannam@134: Capability::Client membrane(Capability::Client inner, kj::Own policy); cannam@134: // Wrap `inner` in a membrane specified by `policy`. `inner` is considered "inside" the membrane, cannam@134: // while the returned capability should only be called from outside the membrane. cannam@134: cannam@134: Capability::Client reverseMembrane(Capability::Client outer, kj::Own policy); cannam@134: // Like `membrane` but treat the input capability as "outside" the membrane, and return a cannam@134: // capability appropriate for use inside. cannam@134: // cannam@134: // Applications typically won't use this directly; the membraning code automatically sets up cannam@134: // reverse membranes where needed. cannam@134: cannam@134: template cannam@134: ClientType membrane(ClientType inner, kj::Own policy); cannam@134: template cannam@134: ClientType reverseMembrane(ClientType inner, kj::Own policy); cannam@134: // Convenience templates which return the same interface type as the input. cannam@134: cannam@134: template cannam@134: typename ServerType::Serves::Client membrane( cannam@134: kj::Own inner, kj::Own policy); cannam@134: template cannam@134: typename ServerType::Serves::Client reverseMembrane( cannam@134: kj::Own inner, kj::Own policy); cannam@134: // Convenience templates which input a capability server type and return the appropriate client cannam@134: // type. cannam@134: cannam@134: template cannam@134: Orphan::Reads> copyIntoMembrane( cannam@134: Reader&& from, Orphanage to, kj::Own policy); cannam@134: // Copy a Cap'n Proto object (e.g. struct or list), adding the given membrane to any capabilities cannam@134: // found within it. `from` is interpreted as "outside" the membrane while `to` is "inside". cannam@134: cannam@134: template cannam@134: Orphan::Reads> copyOutOfMembrane( cannam@134: Reader&& from, Orphanage to, kj::Own policy); cannam@134: // Like copyIntoMembrane() except that `from` is "inside" the membrane and `to` is "outside". cannam@134: cannam@134: // ======================================================================================= cannam@134: // inline implementation details cannam@134: cannam@134: template cannam@134: ClientType membrane(ClientType inner, kj::Own policy) { cannam@134: return membrane(Capability::Client(kj::mv(inner)), kj::mv(policy)) cannam@134: .castAs(); cannam@134: } cannam@134: template cannam@134: ClientType reverseMembrane(ClientType inner, kj::Own policy) { cannam@134: return reverseMembrane(Capability::Client(kj::mv(inner)), kj::mv(policy)) cannam@134: .castAs(); cannam@134: } cannam@134: cannam@134: template cannam@134: typename ServerType::Serves::Client membrane( cannam@134: kj::Own inner, kj::Own policy) { cannam@134: return membrane(Capability::Client(kj::mv(inner)), kj::mv(policy)) cannam@134: .castAs(); cannam@134: } cannam@134: template cannam@134: typename ServerType::Serves::Client reverseMembrane( cannam@134: kj::Own inner, kj::Own policy) { cannam@134: return reverseMembrane(Capability::Client(kj::mv(inner)), kj::mv(policy)) cannam@134: .castAs(); cannam@134: } cannam@134: cannam@134: namespace _ { // private cannam@134: cannam@134: OrphanBuilder copyOutOfMembrane(PointerReader from, Orphanage to, cannam@134: kj::Own policy, bool reverse); cannam@134: OrphanBuilder copyOutOfMembrane(StructReader from, Orphanage to, cannam@134: kj::Own policy, bool reverse); cannam@134: OrphanBuilder copyOutOfMembrane(ListReader from, Orphanage to, cannam@134: kj::Own policy, bool reverse); cannam@134: cannam@134: } // namespace _ (private) cannam@134: cannam@134: template cannam@134: Orphan::Reads> copyIntoMembrane( cannam@134: Reader&& from, Orphanage to, kj::Own policy) { cannam@134: return _::copyOutOfMembrane( cannam@134: _::PointerHelpers::Reads>::getInternalReader(from), cannam@134: to, kj::mv(policy), true); cannam@134: } cannam@134: cannam@134: template cannam@134: Orphan::Reads> copyOutOfMembrane( cannam@134: Reader&& from, Orphanage to, kj::Own policy) { cannam@134: return _::copyOutOfMembrane( cannam@134: _::PointerHelpers::Reads>::getInternalReader(from), cannam@134: to, kj::mv(policy), false); cannam@134: } cannam@134: cannam@134: } // namespace capnp cannam@134: cannam@134: #endif // CAPNP_MEMBRANE_H_