9 ms·
The key paragraph: > The Deno CLI works like a browser, but for code. You import a URL in the code and Deno will go and fetch that code and cache it locally, j
by paxys 6y ago
The key paragraph:
> The Deno CLI works like a browser, but for code. You import a URL in the code and Deno will go and fetch that code and cache it locally, just like a browser. Also, like a browser, your code runs in a sandbox, which has zero trust of the code you are running, irrespective of the source. You, the person invoking the code, get to tell that code what it can and can’t do, externally. Also, like a browser, code can ask you permission to do things, which you can choose to grant or deny.
The big problem with Deno is that permissions, once granted, apply to every imported URL. You cannot ask it to let one script access the file system, another access network and the rest of them run fully sandboxed. This makes it so that you either only import scripts you already fully trust (making the permission system useless) or don't allow any access (making the ecosystem useless).
- chii 6y ago> ask it to let one script access the file system, another access network and the rest of them run fully sandboxed. this is actually quite a difficult problem to solve. You're balancing the security needs with usability. Browsers have an advantage on this aspect, because they can make the assumption that the webpage does not require filesystem access. i think fully sandboxed OS-esque security model is the only way this can work. Like on android, where each app sees only their own filesystem, and app-to-app interaction is done via a permission based system that the user has to approve.
- bryanrasmussen 6y agoThey could have maybe looked at E for some inspiration on how to solve the problem http://erights.org/ http://erights.org/
- aabbcc1241 6y agoOn android the apps has access to shared folders. For example my music player can scan and read files under /mnt/sdcard/Android/data/com.dropbox.android/files/ It maybe more isolated if it follows the nix file system model?
- freeopinion 6y agoWould you please clarify what you are talking about? You grant permissions on a script by script basis. Your statement looks to me like the exact opposite of reality. What have I misunderstood?
- csande17 6y agoI think you and the parent are working under different definitions of "script". Deno allows you to grant permissions per top-level invocation. So if you have one program that you run by typing `deno run passwordmanager.js` at the console, and another program that you run by typing `deno run downloadfiles.js`, you can give different permissions to each of those "scripts". But within one program, you can't (easily) give different permissions to different dependencies. If downloadfiles.js imports both http.js and check-if-number-is-even.js, and it wants http.js to be able to access the network, it has to request the access-the-network permission globally. So check-if-number-is-even.js would also be able to access the network. The different "script" files that make up one program all have to have the same permissions. (Sure, Deno might have other ways to sandbox parts of your program, but so does Node -- Deno's permissions improvements don't really help you in that case.)
- bigyikes 6y agoCould the solution just be to audit the permissions your dependencies require? Sure, it gets murkier with transitive deps like your http.js and number-is-even.js example, but I would argue that this scenario isn’t as dangerous as it seems because it adds an opportunity for the middle-man-dependency (http.js) to catch overreaching permissions. With node, it is very opaque. With deno, as I see it, http.js can easily check the permissions for number-is-even.js, and you can easily check the permissions of http.js. It’s not perfect, but I think each link in the dependency chain is at least more easily auditable, even if it is not strictly more secure.
- bkolobara 6y agoIn my experience, auditable doesn't really matter. To have peace of mind you really need to be able to enforce that number-is-even.js will never do a http request.
- deleted 6y ago[deleted]
- half-kh-hacker 6y agoconst status = await Deno.permissions.revoke({ name: "run" }); assert(status.state !== "granted") import * from "https://shady-site.com/this-file-cannot-run-processes.ts"
- datalist 6y agoThough after that point even your own code cannot use that permission anymore.
- martin-adams 6y agoIt would be amazing if it had scoped permissions.
- jxub 6y agoI think Ryan is aware of this as it has been raised in some ocasions already, but it might be too complicated or costly in dev time to have before a new version bump.
- Vinnl 6y agoTo keep with the browser comparison: browsers have started to add tracking protection, and people are installing adblockers, because we've basically concluded that we don't want the websites we load to call out to arbitrary other websites, even if we do want them to call out to some. That said, sounds like it's something they're thinking about: > It is also hard to break down those permissions, to say “this code can do this, but this other code over here can’t” or when code prompts to escalate privileges where is that code coming from. Hopefully we can figure out an easy to use mechanism coupled with something that would be effective and performant at runtime to try to solve those challenges.
- asiachick 6y agoExcept it's not a browser which never has file access, db access etc.... A MITM download in the browser affects a few users. A MITM download in Deno effects all users.
- Vinnl 6y agoLet me tell you about IndexedDB and the File System API :) Jokes aside, though, doesn't the MITM only affect users who run the MITM'd script, just like in the browser it only affects users who visit a MITM'd site?
- PudgePacket 6y ago... Just like every other software dependency system ever.
- hombre_fatal 6y agoDoesn't solve the problem, but you can at least provide a whitelist of domains and filesystem paths. For example, if you only whitelisted --allow-net=api.example.com, it would be a lot more annoying for a rogue dependency to exfiltrate data.