3 ms·

Looked around your readme and wiki but didn't see anything about this vs. deno? Both are Rust wrappers around V8 with privilege mechanisms. Am I missing anythin

• tlhunter 7y ago
  Good question! Deno has four policies that I know of: --allow-write --allow-net --allow-env --allow-run Today these policies are all-or-nothing and they are global to the entire Deno process. Consider and application which _only_ needs to make a GET request to a single GitHub API endpoint. This application will then use the `--allow-net` flag and will be able to communicate with arbitrary sites like evil.ru. However, with Osgood, the permissions are much more granular. One can specify a policy to only get access to _exactly_ what is needed. The permissions are also granular enough to only apply to a subset of the overall application: app.route('GET', '/gh/:username', 'gh.js', policy => { policy.outboundHttp.allowGet('https://api.github.com/users/*/gists'); }); We will add further policies where it makes sense, such as with filesystem access. However, Osgood doesn't aim to be a _general_ platform for running code, so we will likely expose filesystem access in a manner akin to this: https://thomashunter.name/presentations/introducing-osgood/#/39 https://thomashunter.name/presentations/introducing-osgood/#...
  • krzkaczor 7y ago
    Having the ability to whitelist particular URLs (or at least domains) is really really cool. This would prevent (or make much harder) many of previous npm packages hacks. Maybe you guys should work together with deno team on exchanging these ideas? Anyway, great work!
  • teleclimber 7y ago
    > Today these policies are all-or-nothing No, Deno supports whitelists for net and file access: https://deno.land/manual.html#permissionswhitelist https://deno.land/manual.html#permissionswhitelist