Vidalia complains about bridge line starting with "bridge"
|Reported by:||karsten||Owned by:||chiiph|
|Actual Points:||Parent ID:||#6434|
When I fetch new bridges from bridges.tpo and copy-paste a line into Vidalia's Network tab (including the "bridge" part), I get the following error messages:
Aug 29 08:37:14.573 [Warning] Error parsing Bridge address 'bridge' Aug 29 08:37:14.574 [Warning] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details.
The obfsproxy TBB has the following error message for me:
Aug 29 08:33:55.497 [Warning] We were supposed to connect to bridge '(scrubbed)' using pluggable transport 'bridge', but we can't find a pluggable transport proxy supporting 'bridge'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
Can we make Vidalia smarter by ignoring the "bridge" part in bridge lines? We can probably get asn's promise to never call a pluggable transport "bridge". ;)