Is “fly launch –dockerfile” safe to use with untrusted Dockerfiles? [REPOST]

, , ,
1

As part of a system to run untrusted user code, I’ve considered allowing users to define their own execution environments using a Dockerfile.

So: is calling “fly launch --dockerfile pathToUserDockerfile --name someUserApp” safe? That is, is there some Dockerfile that would allow a user to gain control of the machine calling “fly launch”?

(Reposted from: Is "fly launch --dockerfile" safe to use with untrusted Dockerfiles?)

2

I wish I had enough security chops to give you a definitive answer, but my understanding is that what you described is intended to be safe, with (at least?) two caveats:

  • for you to run fly launch you need an access token or macaroon. If you make that secret available to the app you launched, that app can do some mischief.
  • if you launch an app in the same org as your machine, it will be in the same private network. If your machine has ports open, it can access them.
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.