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

dynamically apply #73

Open
alisaosipova opened this issue Jul 16, 2024 · 8 comments
Open

dynamically apply #73

alisaosipova opened this issue Jul 16, 2024 · 8 comments

Comments

@alisaosipova
Copy link

Can I dynamically apply a decision to problematic traffic about what to do with it (accept/drop)? Possibly using Pass rules from sslproxy.conf
Let’s say an error occurred with some traffic while the program was running, I want to decide what to do with the problematic traffic, let it pass without decrypting it or drop it
It is worth clarifying that it is not known in advance what kind of traffic it will be, and also that I do not want to let ALL traffic through without decryption, etc.

thx

@sonertari
Copy link
Owner

You can try the Passthrough option (the -P option), globally, per proxyspec, or per filter rule. But it may or may not cover all the error conditions you want.

@alisaosipova
Copy link
Author

You can try the Passthrough option (the -P option), globally, per proxyspec, or per filter rule. But it may or may not cover all the error conditions you want.

That is, there is no dynamic decision-making? Is it possible to implement the following: dynamically add a rule to sslproxy.conf and update it without restarting the service itself (in this case the rule will appear)

@sonertari
Copy link
Owner

sonertari commented Jul 16, 2024

On certain ssl errors, the passthrough mode passes those connections through, which can be considered dynamic.
But sslproxy does not have the config reload that you describe.
And here as well.

@alisaosipova
Copy link
Author

On certain ssl errors, the passthrough mode passes those connections through, which can be considered dynamic. But sslproxy does not have the config reload that you describe. And here as well.

I don't think this is quite what I'm looking for. I don't need SSLproxy to work only in Passthrough mode, because then it passes ALL traffic, I need to pass specific traffic, but which is UNKNOWN until that traffic itself is received. I hope you could understand me

Do you think restarting the config is possible without turning off the service? It’s logical that I’ll do this function myself.

@alisaosipova
Copy link
Author

and I want to process the rest of the traffic as before, via the SSL protocol.

@sonertari
Copy link
Owner

No, Passthrough mode does not work like that, it passes the connection through on error (something like fail-open).
Filter rules and proxyspecs are hard to reload without restarting sslproxy.

@alisaosipova
Copy link
Author

On certain ssl errors, the passthrough mode passes those connections through, which can be considered dynamic. But sslproxy does not have the config reload that you describe. And here as well.

I don’t understand what kind of errors this happens. could you describe the list to me?

@sonertari
Copy link
Owner

For example, it happens on SSL errors while connecting to server.
Or on errors creating SSL context, e.g. while forging server cert.
You can follow the links to sources for details.

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