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

verify Ziti's server cert #292

Open
qrkourier opened this issue Apr 7, 2023 · 2 comments
Open

verify Ziti's server cert #292

qrkourier opened this issue Apr 7, 2023 · 2 comments
Assignees
Labels
enhancement Enhancement of an existing feature
Milestone

Comments

@qrkourier
Copy link
Member

zrok should verify Ziti's server certificate before transmitting the Ziti login password

@qrkourier
Copy link
Member Author

A new zrok controller config directive like ca_certs or tls_trust_bundle would be great. It could accept a PEM bundle as a string or file path or both.

@michaelquigley michaelquigley added the enhancement Enhancement of an existing feature label Apr 14, 2023
@michaelquigley michaelquigley added this to the v0.5 milestone Apr 14, 2023
@qrkourier qrkourier self-assigned this Dec 14, 2023
@qrkourier
Copy link
Member Author

While working my way back to this, I've mitigated the risk in my zrok instances with two approaches in this order:

  1. two containers (sidecar pattern) or processes sharing a network interface and communicating exclusively via IPC over IP on the loopback interface (ziti mgmt API is not exposed nor published)
  2. two containers in an isolated bridge network communicating exclusively at layer 2 (LAN) (ziti mgmt API is exposed but not published)

@michaelquigley michaelquigley modified the milestones: v1.0, v1.1 Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of an existing feature
Projects
Development

No branches or pull requests

2 participants