News for hackers. Stuff that matters.
Re:Deno 1.9 by croes on Wednesday April 14, 2021 @12:17AM (#26802885)
It's main selling point is security. With Deno you can provide permission to scripts using flags. Deno offers a sandbox security layer through permissions. List of the flags:

--allow-env allow environment access.

--allow-hrtime allow high resolution time measurement.

--allow-net=<allow-net> allow network access.

--allow-plugin allow loading plugins.

--allow-read=<allow-read> allow file system read access.

--allow-run allow running subprocesses.

--allow-write=<allow-write> allow file system write access.

--allow-all allow all permissions (same as -A)

Re:Deno 1.9 by kybernetikos on Wednesday April 14, 2021 @02:32AM (#26803667)
What I dislike is that you provide these permissions for the whole process. I'd like it to be more that you can constrain and pass the permissions down to libraries like capabilities.
Re:Deno 1.9 by beaker52 on Wednesday April 14, 2021 @03:00AM (#26803868)
I agree. I hear a lot made of Deno's "security" but process flags don't really make me feel much more secure when I've had to enable most of them anyway. At that point they just start getting in the way and giving me a false sense of security.
Re:Deno 1.9 by pocketgrok on Monday April 19, 2021 @02:11PM (#26866131)
My understanding is that the current security flags model isn't really meant to be the final solution. They wanted to ensure that the browser security model isn't simply dropped like it is in Node, but to improve it further they'll probably need outside help.