Object-capability security in Racket? -
racket's sandbox seems great running code don't trust, prevent modules call 1 in sandbox being able see or modify 1 another's internal state, code, or behavior. right best way can think of separate sandboxes , modified "require" wraps exported functions in contracts create proxies. there better way?
could provide concrete example?
if module requires module b, module can't see inside b. module can use functions module b explicitly provided. of these might change internal state in module b.
Comments
Post a Comment