search

agabani / tor-operator

Tor Operator is a Kubernetes Operator that manages Onion Balances, Onion Keys and Onion Services to provide a highly available, load balanced and fault tolerate Tor Ingress and Tor Proxy.
https://agabani.github.io/tor-operator/docs/
MIT License
9 stars 3 forks source link

access to control port of an OnionService / exposing of port inside cluster as service #208

Closed some0ne2 closed 7 months ago

some0ne2 commented 7 months ago

I already found the comparison sheet of this repo "against" bugfests repo.

I would like to use the control port on an OnionService to be able to kill specific onion curcuits to prevent flooding attacks. Is it possible to expose this port using this repo / any hints on how to do this? Using bugfests library it's not possible at the moment. Seems like this is a requirement for many "nerdy" users of this setup.

Thanks in advance!

agabani commented 7 months ago

In the current architecture, the tor container in the onion-balance pod binds the control port to 127.0.0.1:6666, All containers within the same pod can then connect to the control port (example: onion-balance container).

tor-operator-baseline

This pattern could be extended to allow end-users to provide their own containers (example: sidecar-1 ... sidecar-n). This is similar to how extensions work in Envoy.

tor-operator-proposal

I would like to use the control port on an OnionService to be able to kill specific onion curcuits to prevent flooding attacks.

In your use-case, could your extension be packaged as a container to be deployed inside every pod?

github-actions[bot] commented 7 months ago

This issue is stale because it has been open for 14 days with no activity.

github-actions[bot] commented 7 months ago

This issue was closed because it has been inactive for 7 days since being marked as stale.