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

Is that possible to import the all packet data to request header like getting source/destination ip/port via req.Header.Get("SslProxy") ? #67

Open
samueljaydan opened this issue Jun 12, 2024 · 4 comments

Comments

@samueljaydan
Copy link

No description provided.

@sonertari
Copy link
Owner

Listening program should parse the SSLproxy line in the first packet of a connection to get the source and destination addresses, as explained in README, if I understand your question right.

@samueljaydan
Copy link
Author

samueljaydan commented Jun 12, 2024

Thanks for the answer.
Yes you've explained, but I need all packet data, so I can decode other layers also not just the source/destination ip/port. Is that possible to redirect full packet data from your SSLproxy to Listening program. If it is, how to do that?

@samueljaydan samueljaydan changed the title Is that possible to import the packet data to request header like getting source/destination ip/port via req.Header.Get("SslProxy") ? Is that possible to import the all packet data to request header like getting source/destination ip/port via req.Header.Get("SslProxy") ? Jun 12, 2024
@sonertari
Copy link
Owner

Yes, that's the purpose of SSLproxy with a listening program. See the sample lp program, which is used with e2e tests too.

@samueljaydan
Copy link
Author

I see, As I understand it, this is redirected by default without adding any config options. just to be able to access this part from the user space.

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