Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

kyushu.dev

Post reply on HN
Print view View original

31–40 of 44 posts

Re: Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

#32

Post by zuzululu »

Nzen wrote: post #12
jahala wrote: post #3

Loving the customer testimonials :D .. If someone feels like an eli5 - What are the use-cases for something like this?

I think that this is a plugin library for teams that want to offer a platform for the public (or an LLM-AI) to submit code to. If your team writes some code, you don't generally sandbox it from yourself, you just amend your program: you don't need a sandbox. But, if you want to run code that you don't trust, you should run it in a way that prevents it from causing problems if it is actually dangerous (like a virus or…

how is it different from firecracker or other containerization ? what makes it secure enough to make those claims?

Re: Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

#34

Post by le_chuck »

zuzululu wrote: post #31

so am I able to migrate my current cloudflare worker API to this ?

I wouldn't rush and jump straight to it at this point, as mentioned it's early and relatively experimental at this point, but technically, at least for relatively simple function, yes.

As a matter of fact, I did it myself in one of my pipelines. Here's the related PR https://github.com/peterpeterparker/blog-to-newsletter-worke...

Re: Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

#35

Post by zuzululu »

le_chuck wrote: post #34
zuzululu wrote: post #31

so am I able to migrate my current cloudflare worker API to this ?

I wouldn't rush and jump straight to it at this point, as mentioned it's early and relatively experimental at this point, but technically, at least for relatively simple function, yes. As a matter of fact, I did it myself in one of my pipelines. Here's the related PR https://github.com/peterpeterparker/blog-to-newsletter-worke...

interesting I think if I could migrate off cloudflare and sort of have a hybrid back up in case cloudflare goes down again

Looking forward to see more developments on this as it has real economic value if it does work.

Re: Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

#37

Post by mcapodici »

Lerc wrote: post #28

It raises the interesting question of what is the best isolation for a browser side sandbox. Running a worker. Running a worker running a js implementation. Running a worker running a wasm module running a js implementation (quickjs) running some passed code. Running a worker running what kyu build runs. And then of course the possibility of a environment where you pass it an integer n and it geneates n levels of. Ne…

Or just an iframe?

Re: Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

#38

Post by Lerc »

nolist_policy wrote: post #30
Lerc wrote: post #28

It raises the interesting question of what is the best isolation for a browser side sandbox. Running a worker. Running a worker running a js implementation. Running a worker running a wasm module running a js implementation (quickjs) running some passed code. Running a worker running what kyu build runs. And then of course the possibility of a environment where you pass it an integer n and it geneates n levels of. Ne…

The best isolation is inside a Service Worker, where the script is served with Content-Security-Policy: sandbox header.[1] [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...

I'm not sure if service workers are particularly amenable to having Developer A provide an interface for User B to run untrusted code made by Developer C, D and E.
Post reply on HN