←back to thread

Yt-dlp: External JavaScript runtime now required for full YouTube support

(github.com)
856 points bertman | 6 comments | 12 Nov 25 10:12 UTC | HN request time: 0.879s | source | bottom
Show context
djoldman ◴[12 Nov 25 12:54 UTC] No.45899558[source]▶
From

https://github.com/yt-dlp/yt-dlp/wiki/EJS

it looks like deno is recommended for these reasons:

> Notes

> * Code is run with restricted permissions (e.g, no file system or network access)

> * Supports downloading EJS script dependencies from npm (--remote-components ejs:npm).

replies(2): >>45900422 #>>45900960 #
arbll ◴[12 Nov 25 14:11 UTC] No.45900422[source]▶
It's fine for this project since google is probably not in the business of triggering exploits in yt-dlp users but please do not use deno sandboxing as a your main security measure to execute untrusted code. Runtime-level sandboxing is always very weak. Relying on OS-level sandboxing or VMs (firecracker & co) is the right way for this.
replies(3): >>45900665 #>>45903690 #>>45907042 #
1. zahlman ◴[12 Nov 25 21:32 UTC] No.45907042[source]▶
> Runtime-level sandboxing is always very weak. Relying on OS-level sandboxing or VMs (firecracker & co) is the right way for this.

... Isn't the web browser's sandboxing runtime-level?

replies(2): >>45907339 #>>45907618 #
2. franga2000 ◴[12 Nov 25 21:56 UTC] No.45907339[source]▶
Yes, and it's only reasonably secure because of years of exploits being found and fixed by some of the best (and very well-funded) software security engineers out there.
replies(2): >>45907609 #>>45907635 #
3. NoahZuniga ◴[12 Nov 25 22:17 UTC] No.45907609[source]▶
Great news! Deno uses the same runtime as chrome, so you benefit from all those found exploits.
replies(1): >>45907707 #
4. arbll ◴[12 Nov 25 22:17 UTC] No.45907618[source]▶
It used to be 100% runtime-level and it was the golden age of browser exploits. Each of your tabs are now a separate process that the OS sandboxes. They can only access a specific API over IPC for anything that goes beyond js/rendering (cookie management, etc...). An exploit in V8 today only gives access to this API. A second exploit is needed in this API to escape the sandbox and do anything meaningful on the target system.
5. arbll ◴[12 Nov 25 22:18 UTC] No.45907635[source]▶
That's not true. It's secure because they are stacking OS-sandboxing on top, forcing attackers to find a chain of exploits instead of a single issue in V8
6. arbll ◴[12 Nov 25 22:24 UTC] No.45907707{3}[source]▶
While you benefit from the V8 fixes it lacks OS-level sandboxing (see above). Chrome is safe because it stacks security layers. Runtime sandboxing is just one of them and arguably the weakest one.