[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] tor-relays Digest, Vol 157, Issue 19



+1 incoming.




On Tuesday, February 27th, 2024 at 04:17, tor-relays-request@xxxxxxxxxxxxxxxxxxxx <tor-relays-request@xxxxxxxxxxxxxxxxxxxx> wrote:

> 
> 
> Send tor-relays mailing list submissions to
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> or, via email, send a message with subject or body 'help' to
> tor-relays-request@xxxxxxxxxxxxxxxxxxxx
> 
> You can reach the person managing the list at
> tor-relays-owner@xxxxxxxxxxxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tor-relays digest..."
> 
> 
> Today's Topics:
> 
> 1. bridges for Lox (meskio)
> 2. Re: bridges for Lox (Toralf F?rster)
> 3. Re: bridges for Lox (Toralf F?rster)
> 4. Re: bridges for Lox (meskio)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 26 Feb 2024 20:07:45 +0100
> From: meskio meskio@xxxxxxxxxxxxxx
> 
> To: tor-relays tor-relays@xxxxxxxxxxxxxxxxxxxx
> 
> Subject: [tor-relays] bridges for Lox
> Message-ID: 170897446522.1760.2953283832616396350@localhost
> 
> Content-Type: text/plain; charset="utf-8"
> 
> Hello,
> 
> We are developing a reputation based bridge distributor called Lox[0] and are
> preparing to make a call for users to test it in Tor Browser Alpha. In order to
> do this, we need to have some new bridges that can be distributed by Lox. Do you
> want to give us a hand running a bridge (or few) for Lox? At the moment we're
> looking for 10 new bridges for Lox.
> 
> Rdsys, the new bridgeDB, will not automatically assign bridges to Lox for now,
> but will instead accept bridges with the 'BridgeDistribution lox' configured in
> torrc.
> 
> To set up a bridge for Lox, configure a normal obfs4 bridge[1] and simply
> include the following line in torrc:
> BridgeDistribution lox
> 
> As Lox is only going to be released for testing, you might not see a lot of
> traffic on Lox bridges at the moment. However, these bridges will be very useful
> for us to improve Lox and see what works and what does not.
> 
> Thank you
> 
> 
> [0] https://gitlab.torproject.org/tpo/anti-censorship/lox
> [1] https://community.torproject.org/relay/setup/bridge/
> 
> --
> meskio | https://meskio.net/
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> My contact info: https://meskio.net/crypto.txt
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Nos vamos a Croatan.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: signature
> URL: http://lists.torproject.org/pipermail/tor-relays/attachments/20240226/658c1e8e/attachment-0001.sig
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 26 Feb 2024 21:03:13 +0100
> From: Toralf F?rster toralf.foerster@xxxxxx
> 
> To: tor-relays@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-relays] bridges for Lox
> Message-ID: 7ea7df6d-36a3-463b-be55-0e1c72179cd0@xxxxxx
> 
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> On 2/26/24 20:07, meskio wrote:
> 
> > At the moment we're
> > looking for 10 new bridges for Lox.
> 
> 
> 9 left
> 
> --
> Toralf
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 26 Feb 2024 21:07:50 +0100
> From: Toralf F?rster toralf.foerster@xxxxxx
> 
> To: tor-relays@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-relays] bridges for Lox
> Message-ID: e92d9716-99d0-43ca-8959-0727aa1d3221@xxxxxx
> 
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> On 2/26/24 20:07, meskio wrote:
> 
> > Rdsys, the new bridgeDB, will not automatically assign bridges to Lox for now,
> > but will instead accept bridges with the 'BridgeDistribution lox' configured in
> > torrc.
> 
> 
> BTW by accident I configured "any" but restarted tor with "lox" 2
> minutes later. Does that work?
> 
> And FWIW:
> 
> root@luchs:~# grep lox /var/log/tor/notice.log
> Feb 26 20:03:50.008 [warn] Unrecognized BridgeDistribution value "lox".
> I'll assume you know what you are doing...
> 
> root@luchs:~# tor --version
> Tor version 0.4.9.0-alpha-dev (git-b0b943a1613e2f9b).
> Tor is running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11,
> Zlib 1.2.13, Liblzma N/A, Libzstd N/A and Glibc 2.36 as libc.
> Tor compiled with GCC version 12.2.0
> 
> --
> Toralf
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 27 Feb 2024 10:17:33 +0100
> From: meskio meskio@xxxxxxxxxxxxxx
> 
> To: tor-relays@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-relays] bridges for Lox
> Message-ID: 170902545330.1760.4318596201052842335@localhost
> 
> Content-Type: text/plain; charset="utf-8"
> 
> Quoting Toralf F?rster via tor-relays (2024-02-26 21:07:50)
> 
> > On 2/26/24 20:07, meskio wrote:
> > 
> > > Rdsys, the new bridgeDB, will not automatically assign bridges to Lox for now,
> > > but will instead accept bridges with the 'BridgeDistribution lox' configured in
> > > torrc.
> > 
> > BTW by accident I configured "any" but restarted tor with "lox" 2
> > minutes later. Does that work?
> 
> 
> Yes, it looks good from here and lox is already aware of it. Thank you for
> setting it up so fast.
> 
> > And FWIW:
> > 
> > root@luchs:~# grep lox /var/log/tor/notice.log
> > Feb 26 20:03:50.008 [warn] Unrecognized BridgeDistribution value "lox".
> > I'll assume you know what you are doing...
> 
> 
> Yes, you can ignore this log line. Lox is not yet on the list of recognized
> distributors:
> https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/576
> 
> > root@luchs:~# tor --version
> > Tor version 0.4.9.0-alpha-dev (git-b0b943a1613e2f9b).
> > Tor is running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11,
> > Zlib 1.2.13, Liblzma N/A, Libzstd N/A and Glibc 2.36 as libc.
> > Tor compiled with GCC version 12.2.0
> 
> 
> :)
> 
> 
> --
> meskio | https://meskio.net/
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> My contact info: https://meskio.net/crypto.txt
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Nos vamos a Croatan.
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> ------------------------------
> 
> End of tor-relays Digest, Vol 157, Issue 19
> *******************************************
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays