You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it is in the scope of this project, but creating an ephemeral hidden service would - I think - allow for a much nicer API where the transport can manage the life-cycle of the transport and know about all the mappings etc.
It would then obviously be a Tor-specific transport but as described in #1 this transport is already specific to Tor, it just not obvious from the name :)
I think there are two main use-cases here:
Have a general-purpose socks5 transport. If we can land Remove onion_map #2 and Only supports Tor target addresses #1, I think that is achieved. Such a general-purpose socks5 transport allows users to use self-managed Tor hidden services.
Have a dedicated Tor transport that uses ephemeral hidden services and manages them completely by itself.
Tor supports "ephemeral hidden services": https://stem.torproject.org/api/control.html#stem.control.Controller.create_ephemeral_hidden_service
Not sure if it is in the scope of this project, but creating an ephemeral hidden service would - I think - allow for a much nicer API where the transport can manage the life-cycle of the transport and know about all the mappings etc.
It would then obviously be a Tor-specific transport but as described in #1 this transport is already specific to Tor, it just not obvious from the name :)
I think there are two main use-cases here:
onion_map#2 and Only supports Tor target addresses #1, I think that is achieved. Such a general-purpose socks5 transport allows users to use self-managed Tor hidden services.