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

Feature: Onionservice port different from exposed port #5

Open
langfingaz opened this issue Sep 12, 2020 · 0 comments
Open

Feature: Onionservice port different from exposed port #5

langfingaz opened this issue Sep 12, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@langfingaz
Copy link
Contributor

langfingaz commented Sep 12, 2020

Current Situation

One can specify ONIONSERVICE_PORT in case a web service container has multiple ports exposed. This will result in the following line in torrc:

HiddenServicePort <ONIONSERVICE_PORT> <IP>:<ONIONSERVICE_PORT>

If one accesses the onion service, one has to append ":<ONIONSERVICE_PORT>" to the onion link.

Feature Request

It would be great to have two environment variables for web service containers that go into the generated torrc file:

  • VIRTUAL_PORT
    • If set, use this port of to connect with the service. Useful if a service has more than one port exposed. If this is not set but just one port is exposed, use that port.
  • ONIONSERVICE_PORT
    • If ONIONSERVICE_PORT is set, one can access the onionservice via this port. If it is not set, use the chosen virtual port instead.

Benefits

The above line in torrc would change to:

HiddenServicePort <ONIONSERVICE_PORT> <IP>:<VIRTUAL_PORT>

Even if VIRTUAL_PORT is e.g. 4040, one can still specify ONIONSERVICE_PORT=80 and visit the onion service just with the blank onion link.

@langfingaz langfingaz changed the title Feature: Feature: Onionservice port different from exposed port Sep 12, 2020
@moba moba added the enhancement New feature or request label Sep 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants