#11211: Multiple ServerTransportListenAddr entries should be allowed per
transport.
-------------------------------------------------+-------------------------
Reporter: yawning | Owner: kaie
Type: enhancement | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| 0.3.0.x-final
Component: Core Tor/Tor | Version: Tor:
| unspecified
Severity: Normal | Resolution:
Keywords: tor-bridge, pt, needs-proposal, | Actual Points:
tor-pt, bridgedb-parsers, 028-triage, ipv6, |
tor-03-unspecified-201612 |
Parent ID: #10629 | Points:
Reviewer: | Sponsor: T/U
-------------------------------------------------+-------------------------
Comment (by kaie):
What do you think about the following alternative approach, which would
make it unnecessary to improve the internals of transport plugins?
- allow tor to spawn multiple instances per transport type
- introduce some sort of aliasing, which allows the use separate transport
configuration lines,
where each use a separate alias name as the key
For example:
# alias transport-to-execute
ServerTransportAlias second-obfs4 obfs4
ServerTransportAlias third-obfs4 obfs4
ServerTransportListenAddr obfs4 1.2.3.4:443
ServerTransportListenAddr second-obfs4 2.3.4.5:443
ServerTransportListenAddr third-obfs4 [2001::2:3:4]:443
ServerTransportOptions obfs4 "abc"
ServerTransportOptions second-obfs4 "def"
ServerTransportOptions third-obfs4 "ghi"
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11211#comment:24>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
