News for hackers. Stuff that matters.
Re:The browser is the sandbox by vbezhenar on Monday January 26, 2026 @03:37AM (#46763216)
Linux kernel is ridden with local privilege escalation vulnerabilities. This approach works for trusted software that you just want to contain, but it won't work for malicious software.
Re:The browser is the sandbox by viraptor on Monday January 26, 2026 @03:52AM (#46763301)
Ridden? There are issues from time to time, but it's not like you can grab the latest, patched Ubuntu LTS and escalate from an unprivileged seccomp sandbox that doesn't include crazy device files.
Re:The browser is the sandbox by vbezhenar on Monday January 26, 2026 @04:05AM (#46763382)
Any sandbox technology works fine until it isn't. It's not like you could escape Java sandbox, but Java applets were removed from the browsers due to issues being found regularly. In the end, browser sandbox is one of the few that billions of people use and run arbitrary code there every day, without even understanding that. The only comparable technology is qemu. I don't think there are many hosters who will hand off user account to a shared server and let you go wild there.
Re:The browser is the sandbox by viraptor on Monday January 26, 2026 @04:11AM (#46763414)
> Any sandbox technology works fine until it isn't.

Tautology is tautology.

> but Java applets were removed from the browsers

Java applets provided more scope compared to the browser itself, not less. They're not really comparable to seccomp or namespaces.

> hosters who will hand off user account to a shared server

There's lots of CI or function runners that expose docker-like environments.

Re:The browser is the sandbox by vbezhenar on Monday January 26, 2026 @05:56AM (#46764142)
> Java applets provided more scope compared to the browser itself, not less. They're not really comparable to seccomp or namespaces.

They are comparable because they provided a restricted sandbox to execute untrusted code.

> There's lots of CI or function runners that expose docker-like environments.

These are running inside VMs.

Re:The browser is the sandbox by graemep on Monday January 26, 2026 @06:07AM (#46764224)
> Java applets were removed from the browsers due to issues being found regularly

Java applets were killed off my MS's attempt at "embrace, extent, extinguish" by bundling an incompatible version of Java with IE, and Sun's legal response to this.

Re:The browser is the sandbox by vbezhenar on Monday January 26, 2026 @07:49AM (#46765012)
No, Microsoft has nothing to do with it. Browsers are controlled by Google and Mozilla and they decided to block Java plugin.
Re:The browser is the sandbox by whywhywhywhy on Monday January 26, 2026 @06:58AM (#46764590)
They never worked nice and always felt slow, unreliable and janky at the time. It’s easy to blame MS but no one was sad to see the back of them.
Re:The browser is the sandbox by graemep on Monday January 26, 2026 @07:00AM (#46764601)
I was fine with the few I used, and Java works much better on the hardware we now have. A lot better than a lot of cross platform things we have now.
Re:The browser is the sandbox by surajrmal on Monday January 26, 2026 @08:58AM (#46765699)
The Linux API surface is massive. And the fact it's written on C leaves lots of room for vulnerabilities. I don't think you need to reach for a VM, but without a slimmer kernel interface, it's difficult to trust the kernel to actually uphold its required duties in the face of adversaries. This is why folks push heavily for microkernels. Chrome needs to work incredibly hard to provide reliable sandboxing as a result.