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

Support mTLS 1.3 #2307

Open
kj4ezj opened this issue Mar 12, 2024 · 0 comments
Open

Support mTLS 1.3 #2307

kj4ezj opened this issue Mar 12, 2024 · 0 comments
Labels
design-review design review required before implementing work discussion enhancement New feature or request triage

Comments

@kj4ezj
Copy link
Contributor

kj4ezj commented Mar 12, 2024

TLS was brought up multiple times while discussing issue 2188 in today's ENF Engineering meeting.

Currently, nodeos does not support any kind of encryption between itself and an API client or reverse-proxy. A service provider would deploy nodeos behind a reverse-proxy, where the reverse-proxy performs TLS termination for API clients. Traffic between the reverse-proxy and nodeos flows unencrypted, leaving it vulnerable to attacks in the event the service provider operates in a shared environment or their network is compromised.

The industry-standard solution is to use a service mesh to encrypt intra-datacenter communication using mTLS. Mutual TLS provides the added benefit of authenticating the reverse-proxy accessing nodeos. Other suggested workarounds included tunneling this traffic through a VPN or SSH.

Another suggestion still was to directly support an Internet-facing API in Leap using a tool like Mongoose.

This ticket tracks mTLS 1.3 support until that design decision is made, and in the event HTTPS support is added to Leap.

@kj4ezj kj4ezj added enhancement New feature or request discussion design-review design review required before implementing work labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-review design review required before implementing work discussion enhancement New feature or request triage
Projects
Status: Todo
Development

No branches or pull requests

2 participants