Using bridges in combination with pluggable transports helps to conceal the fact that you are using Tor, but may slow down the connection compared to using ordinary Tor relays. Like ordinary Tor relays, bridges are run by volunteers unlike ordinary relays, however, they are not listed publicly, so an adversary cannot identify them easily. Can non-transport clients use any bridge by simply not negotiating a transport? There is a "none" pluggable transport type, but I figured that was for debugging purposes.Most Pluggable Transports, such as obfs4, rely on the use of "bridge" relays. Is this really necessary? I couldn't find any documentation that address this. I currently have another tor instance that runs a vanilla bridge configuration (no transports) on a different port.
ServerTransportListenAddr scramblesuit MYIP:PORT2 ServerTransportListenAddr obfs3 MYIP:PORT ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy managed List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" Ĭan a single tor daemon instance provide both non-obfuscated and various other obfuscated transports? Right now, I have one instance that provides both obfs3 and scramblesuit.
Dkim-signature: v=1 a=rsa-sha1 c=relaxed/relaxed d= h=from:content-type :content-transfer-encoding:subject:date:message-id:to :mime-version s=smtpout bh=Q5idL9lVWAnXRQENmXz6Z3+yQXQ= b=SdZ kWPvXCGmHO1hqIy1gAP4P1XwhoebUEPAzkaUncKlovtIxnYs21XEb8VZ5eMsSk1K 9XEuvAL0+PdcxeurwUH1SXTnEaq2CVgyTS/i0/fqQ2cIzfaZU02oslgZO5OcsOcA zoIbHUp1UssZzXeIxT5QcsP2S+m/aRZ8cvZIr70c=.
0 kommentar(er)
