On Sun, 2022-11-13 at 14:43 -0800, Lawrence Ryan wrote:
> So you're suggesting that a user could write code containing a race,
> have that code produce, say, a slice with the wrong length (by
> interleaving the pointer and length/capacity writes), and then use
> that "mixed" slice to compromise
So you're suggesting that a user could write code containing a race, have
that code produce, say, a slice with the wrong length (by interleaving the
pointer and length/capacity writes), and then use that "mixed" slice to
compromise the system. I see what you're saying.
If the site is running
Sounds fun!
Go doesn't prevent race conditions and those can result in undefined
behavior, so I don't think you're safe just restricting imports and
limiting CPU and memory. You need to run code in a sandbox of some sort. I
would look at what the Go playground does.
On Fri, Nov 11, 2022, 10:47
Still under construction: https://BUGFIX-66.com
Site is intended to be like the book Hacker's Delight, but as a game.
Or like professional programming, where you're mostly trying to
understand/modify other people's code.
Or like programming in a post-GPT3 world where you're checking/fixing a
