Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a way to test an app's proxy support and egress policies locally #31

Open
russellhaering opened this issue Oct 3, 2022 · 1 comment

Comments

@russellhaering
Copy link
Contributor

In thinking through what someone would want out of a local enclave simulator, I think the main things that could give people trouble are:

  1. Configuring their app to use the odyn proxy
  2. Tailoring a policy for their app

There are a few more like testing KMS integration that aren't easy to simulate locally, but these actually are. One approach might be:

  1. Add a flag to Odyn that causes it to run in "simulator" mode, where it just forwards traffic directly out to the internet instead of over a vsock (or, forward traffic to the "outside-the-enclave" half of the proxy over TCP instead of vsock), but still enforces policy
  2. Create a CLI command which would build a container almost like the one which would be converted to an EIF, but with the Odyn "simulator" flag set - then just run that container.
@robszumski
Copy link
Contributor

Agreed, I like the simulator container approach. It allows you to touch most of the Enclaver bits that you'd want to test if you're running it for the first time or if you're tweaking your policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants