News for hackers. Stuff that matters.
Re:I'm not a fan of Deno's security model (2024) by hoppp on Sunday November 08, 2026 @11:20AM (#50414563)
Deno has 1 year of official support left...

I liked the security model because at least they had something, unlike node.

Re:I'm not a fan of Deno's security model (2024) by illright on Sunday November 08, 2026 @11:29AM (#50414655)
Node actually took that from Deno, they do have a permission model now: https://nodejs.org/api/permissions.html
Re:I'm not a fan of Deno's security model (2024) by zdragnar on Sunday November 08, 2026 @12:37PM (#50415319)
From their documentation:

> It does not provide security guarantees in the presence of malicious code. Malicious code can bypass the permission model and execute arbitrary code without the restrictions imposed by the permission model.

The permission model is more of a "help developers not accidentally "rm -rf /" their local machine than it is something that helps end users.

Re:I'm not a fan of Deno's security model (2024) by skybrian on Sunday November 08, 2026 @12:59PM (#50415509)
But doesn’t preventing accidents help end users too?
Re:I'm not a fan of Deno's security model (2024) by foldor on Sunday November 08, 2026 @05:42PM (#50418256)
Sure, but it's more footgun protection, and less security. Still useful, but not the same.
Re:I'm not a fan of Deno's security model (2024) by its-summertime on Monday November 09, 2026 @12:36AM (#50421463)
with deno being "The main thing it protects you against is malicious code that isn't smart enough.", does this not practically put them on the same footing?
Re:I'm not a fan of Deno's security model (2024) by arbll on Sunday November 08, 2026 @11:52AM (#50414888)
Something can be worse than nothing when it tricks users into thinking it provides meanigful security guarentees.
Re:I'm not a fan of Deno's security model (2024) by LoganDark on Sunday November 08, 2026 @03:29PM (#50416830)
This. More than users, too. SMS 2FA for instance is like this - it will encourage important services like banks and government applications to omit higher security measures because the visitor is extra verified. When in reality, this is just a boon to attackers, because it's easy to just steal someone's phone number to pass the verification, and then the website's made it even easier for you by not giving you any additional obstacles. No abuse protection or whatever, because clearly you're the user!
Re:I'm not a fan of Deno's security model (2024) by mscdex on Sunday November 08, 2026 @12:25PM (#50415216)
You're better off relying on OS-level security mechanisms. Not only is it more likely to be much safer/secure, but it also means you don't have to worry about compatibility, missing features, etc. when you switch runtimes/software stacks.
Re:I'm not a fan of Deno's security model (2024) by EGreg on Sunday November 08, 2026 @12:55PM (#50415466)
If you like having something for security — even in Node — check out something I invented, called SafeScript.

It’s for executing untrusted code written by others… a large subset of Javascript which guarantees the code can only call the Facades you inject, and you can hook and intercept anything. It works with callbacks and promises.

What’s more is that it runs in WebWorker sandboxes on the web, and uses a proxy to transparently make existing code make same method calls, or use existing objects, like window.document, but to safer versions, which only allow eg createElement.

And because SafeScript automatically awaits every async function, your synchronous calls to HTMLElement methods etc. will be proxied asynchronously and “just work” without changing the original JS code. SafeScript is robust enough that most existing JS components will simply work without changes when ported to SafeScript.

PS: It can also be embedded in PHP, so you can run untrusted handlers there, too, without worrying about PHP’s large security surface.

PPS: SafeScript is deterministic by default, so you can also get the same results across all environments or runs. You can set the random number generator seed yourself, or inject Date.now() as one of your APIs if you want.

Here it is. Should I do a Show HN?

https://github.com/SafeScript/Safescript

Re:I'm not a fan of Deno's security model (2024) by hoppp on Sunday November 08, 2026 @02:21PM (#50416181)
If you want people to notice it then yes, you should do a show.
Re:I'm not a fan of Deno's security model (2024) by EGreg on Sunday November 08, 2026 @04:27PM (#50417487)
Re:I'm not a fan of Deno's security model (2024) by zahlman on Sunday November 08, 2026 @09:05PM (#50420075)
So, what happens to yt-dlp?