network limiting?

[beauxq]

Is there any way to restrict network communication to only pip and github,
so that malicious apworlds couldn't have any other internet communication?

And with this restriction, it would also be good to have an allow-list
if I know a specific apworld talks to specific site, and I want to allow that.

[Soren90]

I guess this would be possible with iptables or something like that. But I kind of feel like this is out of scope of this project.

apworlds are basically just zip files with code inside of it, so I guess the sensible thing to do would be to analyze the code by reading it manually or ask your favorite AI to do it.

The attack surface is also kind of small. The idea of this project is to just run it to generate a game that you can upload to the main site (which works with custom apworlds). This means that it requires a vulnerability in docker for it to escpae the container. A good practice here would be to use docker compose down after use, as this will remove any kind of persistence (except for the bind mounted folders)