Hi all, I have recently converted a bridge to a relay. Its fingerprint is 0D14A4498E7D1854696CC07548653EA4CD3CB2DA.
I wanted to subscribe to Tor Weather but when I try I get the "We could not locate a Tor node with that fingerprint." error.
Searching the web I found it was a common error years ago, but shouldn't be now.
Any ideas about it? Thanks!
Hi all, I have recently converted a bridge to a relay. Its fingerprint is 0D14A4498E7D1854696CC07548653EA4CD3CB2DA.
I wanted to subscribe to Tor Weather but when I try I get the "We could not locate a Tor node with that fingerprint." error.
As far as I know, bridge fingerprints are obfuscated before publishing. Perhaps this is the reason of the error ?
14 Feb 15 14.05, Aeris:
Hi all, I have recently converted a bridge to a relay. Its fingerprint is 0D14A4498E7D1854696CC07548653EA4CD3CB2DA.
I wanted to subscribe to Tor Weather but when I try I get the "We could not locate a Tor node with that fingerprint." error.
As far as I know, bridge fingerprints are obfuscated before publishing. Perhaps this is the reason of the error ?
thanks Aeris, but I'd find it strange if that were the problem: the relay is not a bridge anymore and it appears both on globe.torproject.org and atlas.
Hi
A couple month ago, my new relay needed some days before I could register it on whether, even though it was showing up on Atlas and Globe. I suggest you try again in a few days.
Good luck :-)
On February 14, 2015 2:18:42 PM mattia sowdust@autistici.org wrote:
14 Feb 15 14.05, Aeris:
Hi all, I have recently converted a bridge to a relay. Its fingerprint is 0D14A4498E7D1854696CC07548653EA4CD3CB2DA.
I wanted to subscribe to Tor Weather but when I try I get the "We could not locate a Tor node with that fingerprint." error.
As far as I know, bridge fingerprints are obfuscated before publishing. Perhaps this is the reason of the error ?
thanks Aeris, but I'd find it strange if that were the problem: the relay is not a bridge anymore and it appears both on globe.torproject.org and atlas.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
s I read it, the tor browser bundle 3.x FAQ [1] implies that bridges on windows can use only obfs3 of the provided pluggable transports. Can someone let me know if this is correct?
The obfs3 line (as described in torrc-defaults) works fine, but torrc won't even accept obfs2, let alone fteproxy or flashproxy.
Would torrc in windows accept obfs4 ? - thanks, eliaz
On Mon, 16 Feb 2015 10:30:57 +0000 eliaz eliaz@riseup.net wrote:
s I read it, the tor browser bundle 3.x FAQ [1] implies that bridges on windows can use only obfs3 of the provided pluggable transports. Can someone let me know if this is correct?
Huh? What does a old browser bundle FAQ have to do with running bridges on windows?
The obfs3 line (as described in torrc-defaults) works fine, but torrc won't even accept obfs2, let alone fteproxy or flashproxy.
No one should use obfs2 for anything, it's deprecated.
Would torrc in windows accept obfs4 ? - thanks, eliaz
If you have an obfs4proxy binary compiled for windows, you can run an obfs4 bridge on windows (as well as any of the other transports supported by obfs4proxy, which is currently obfs2/obfs3).
I'm not really understanding the question...
Yawning Angel: On Mon, 16 Feb 2015 10:30:57 +0000 eliaz eliaz@riseup.net wrote:
s I read it, the tor browser bundle 3.x FAQ [1] implies that bridges on windows can use only obfs3 of the provided pluggable transports. Can someone let me know if this is correct?
Huh? What does a old browser bundle FAQ have to do with running bridges on windows?
My apologies if my original query led you astray. It was only about the documentation being less helpful to windows users than it could be:
The FAQ I referenced includes information about Tor Browser 3.x, but only mentions obfs3:
If you've installed Obfsproxy, you'll need to add one more line:
ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
I went to that FAQ after not being able to incorporate any other transport lines into torrc for a windows implementation of the browser by using information in torrc-defaults. Tor documentation often leaves windows users (well, me at least) to figure out for ourselves by way of tedious experiments whether it applies generally, or only to Unix implementations. This was the case in torrc-defaults, which is what led me to wonder whether I had made a mistake when attempting to write the lines into torrc or if indeed the lines, except for obfs3, were inapplicable in windows.
The obfs3 line (as described in torrc-defaults) works fine, but torrc won't even accept obfs2, let alone fteproxy or flashproxy.
No one should use obfs2 for anything, it's deprecated.
Yeah, I know that. I was just illustrating another case where torrc unexpectedly refused to accept a line.
Would torrc in windows accept obfs4 ?
If you have an obfs4proxy binary compiled for windows, you can run an obfs4 bridge on windows (as well as any of the other transports supported by obfs4proxy, which is currently obfs2/obfs3).
Above my pay grade, sorry. I'll get around to it one of these days.
I'm not really understanding the question...
HTH - eliaz
tor-relays@lists.torproject.org
-
Aeris -
eliaz -
Frédéric Cornu -
mattia -
Yawning Angel