Re: [tor-talk] Published bridge?

[Maxxer]

On 6 February 2017 at 15:57, Geoff Down  wrote:

> Redacted information is available by nickname and hashed fingerprint
>

I didn't know, thanks!
Indeed it shows up, but of course IP information is as you said redacted so
it's impossible to understand if IPv6 is properly set up.

Thanks.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Published bridge?

[Geoff Down]

On Mon, Feb 6, 2017, at 10:48 AM, Maxxer wrote:
> On 5 February 2017 at 20:38, Roger Dingledine  wrote:
> 
> > You can search for your nickname or identity fingerprint on
> > https://atlas.torproject.org/
> 
> 
> FWIR bridges are not published into public database. That would make
> useless requesting them via b.t.o...
> -- 
Redacted information is available by nickname and hashed fingerprint -
see the line in the logs
'Your Tor bridge's hashed identity key fingerprint is..'

GD

-- 
http://www.fastmail.com - A fast, anti-spam email service.

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Published bridge?

[Maxxer]

On 5 February 2017 at 20:38, Roger Dingledine  wrote:

> So it is not surprising that you wouldn't find your own bridge on
> https://bridges.torproject.org/ -- you are very likely not on an IP
> address that would map to your bridge.
>

... but it's weird that I get 0 bridges when there are some available.


> You can search for your nickname or identity fingerprint on
> https://atlas.torproject.org/


FWIR bridges are not published into public database. That would make
useless requesting them via b.t.o...
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Published bridge?

[Roger Dingledine]

On Sun, Feb 05, 2017 at 08:15:07PM +0100, Maxxer wrote:
> A couple of days ago I've set up a new bridge. I've tested it in my config
> and works fine

Great! Thanks for setting up a bridge. :)

>, but I've doubts it's getting published on the bridge
> database.
> 
> I've configured it on both IPv4 and IPv6, I've remotely tested IPv6 and the
> connection is established, but when I query the bridgedb for ipv6 only
> bridges it returns nothing.

Yes, bridgedb divides bridges up into different distribution
strategies, and one of those strategies is to give them out by
https://bridges.torproject.org/. For those bridges, it further divides
them up by where on the Internet you're coming from (for ipv4, it
divides by /16. For ipv6, I don't know what bitmask it picks).

So it is not surprising that you wouldn't find your own bridge on
https://bridges.torproject.org/ -- you are very likely not on an IP
address that would map to your bridge.

> How can I know if the bridge is published correctly?

You can search for your nickname or identity fingerprint on
https://atlas.torproject.org/

If you allow javascript, atlas even sends your browser some javascript
that hashes the fingerprint before your browser sends it to atlas, so
atlas never learns the fingerprint (onionoo only stores a hashed version
of bridge identity fingerprints, since if you know the fingerprint,
you can ask the bridge authority for the bridge descriptor and learn
everything else about it).

(If you don't allow javascript, that's fine too -- you send your actual
bridge identity fingerprint to atlas, which hashes it and then discards
the original.)

> This is the node's torrc:
> ExitPolicy reject *:*
> RunAsDaemon 1
> ORPort 9123
> BridgeRelay 1
> ServerTransportPlugin obfs3,obfs4 exec /usr/local/bin/obfs4proxy
> ServerTransportListenAddr obfs3 [::]:443
> ServerTransportListenAddr obfs4 [::]:80
> ExtORPort auto
> PublishServerDescriptor bridge
> 
> Is everything correct?

It looks promising!

--Roger

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

[tor-talk] Published bridge?

[Maxxer]

Hi.
A couple of days ago I've set up a new bridge. I've tested it in my config
and works fine, but I've doubts it's getting published on the bridge
database.

I've configured it on both IPv4 and IPv6, I've remotely tested IPv6 and the
connection is established, but when I query the bridgedb for ipv6 only
bridges it returns nothing.
How can I know if the bridge is published correctly?

The log correctly shows as binding on [::]:
Feb 04 23:46:54.000 [notice] Registered server transport 'obfs3' at
'[::]:443'
Feb 04 23:46:54.000 [notice] Registered server transport 'obfs4' at
'[::]:80'

This is the node's torrc:
ExitPolicy reject *:*
RunAsDaemon 1
ORPort 9123
BridgeRelay 1
ServerTransportPlugin obfs3,obfs4 exec /usr/local/bin/obfs4proxy
ServerTransportListenAddr obfs3 [::]:443
ServerTransportListenAddr obfs4 [::]:80
ExtORPort auto
PublishServerDescriptor bridge

Is everything correct?
thanks
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk