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

Envoy forward proxy - man in the middle with ssl termination #20425

Closed
batistado opened this issue Mar 18, 2022 · 15 comments
Closed

Envoy forward proxy - man in the middle with ssl termination #20425

batistado opened this issue Mar 18, 2022 · 15 comments
Labels
area/tls stale stalebot believes this issue/PR has not been touched recently

Comments

@batistado
Copy link

Hi
I wanted to check if envoy supports Man in the middle with SSL termination as a forward proxy?
If so can you link me to any documentation or example config how to do it?

@daixiang0
Copy link
Member

May be cluster filter or custom HTTP conn pool helps. 🤔

@batistado
Copy link
Author

How? Care to elaborate?

@daixiang0
Copy link
Member

@soulxu maybe you know details.

@soulxu
Copy link
Member

soulxu commented Mar 21, 2022

@soulxu maybe you know details.

@batistado not sure you are asking a normal tls termination or something like what @LuyaoZhong is doing here #18928

@batistado
Copy link
Author

batistado commented Mar 21, 2022

@soulxu No we don't want to envoy to generate a copied cert from upstream service's cert (like www.google.com). My use case is this:

Current setup:
internal service ----> External service

External service presents our org's self signed cert to internal service and internal service verifies it via our org's root CA cert.

Want setup:
internal service ----> Envoy (as forward proxy) ----> External service

We want to able to install our org's self signed cert and root CA to envoy so envoy can mimic External service to internal service and then to external service it behaves like internal service.

@LuyaoZhong
Copy link
Contributor

@batistado I think it is indeed what we are doing with #18928 . We have a workable PR to mimic the server certificate, which might satisfy your requirement.

There are limitations if we don't have the real server cert as reference to mimic cert, for instance we will lose TLS extensions, etc. That's why we are discussing the new workflow on #18928.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Apr 21, 2022
@vorishirne
Copy link

vorishirne commented Apr 22, 2022

@LuyaoZhong I want to test your changes.

So the traffic has to be routed to envoy via iptable rules or some other way, in your example config attached in PR?

@github-actions github-actions bot removed the stale stalebot believes this issue/PR has not been touched recently label Apr 22, 2022
@LuyaoZhong
Copy link
Contributor

@vorishirne Yes, you need to route traffic to Envoy with proper iptables rule set.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label May 24, 2022
@vorishirne
Copy link

@LuyaoZhong is this feature still under development

@LuyaoZhong
Copy link
Contributor

@vorishirne Yes, see the issue TLS bumping .

@github-actions github-actions bot removed the stale stalebot believes this issue/PR has not been touched recently label May 25, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Jun 24, 2022
@github-actions
Copy link

github-actions bot commented Jul 1, 2022

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

@github-actions github-actions bot closed this as completed Jul 1, 2022
@kmushegi
Copy link

This video could be useful? just watched it myself, looking for similar things https://www.youtube.com/watch?v=B8nTc08CeRQ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tls stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

6 participants