From the design stage, Kobako aimed to let the Host and the Guest communicate easily, which is why the Bind service mechanism was designed in the first place.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
Kobako: From Default Allow to Deny — Balancing Convenience and Security
-
Kobako: Why the Sandbox Deliberately Has No Time
Once we finished mechanisms like RPC, Handle, and Block, we already had a pleasant mruby scripting environment.
-
Kobako: Letting Blocks Pass Through the Sandbox
The Kobako: Handle Mechanism isn’t anything special for projects that support a scripting language, but blocks are a capability unique to Ruby, and it would be a shame if we couldn’t make good use of them inside a sandbox.
-
How NVIDIA OpenShell Handles Network Access
Over the weekend I spent some time reading how NVIDIA’s newly released OpenShell achieves network security for its Sandbox.
-
Kobako: Why Native Filesystem Support
Kobako recently moved to v0.28.0, which reworked the design that used to depend heavily on MessagePack.