Re: [tor-relays] Improving Relay IPv6 - RIPE Grant

2019-12-16 Thread Jonathan Sélea
I am unable to see why this is a good idea actually.
As someone said already, I too would be unable to provide bridges and
relays thanks to my ISP (Telia) does not provide an IPv6.
But removing IPv4 only nodes from the network - you are basically
removing a large chunk of relays from the network without any real reason.


On 12/12/2019 5:49 PM, NOC wrote:
>
> Great,
>
> than lets drop all IPv4 only relays from consensus 2020 finally.
>
> P.S. whitelist me so it doesn't take days till my emails appear on the
> mailing list.
>
> Thank you
>
> On 11.12.2019 03:20, teor wrote:
>> Dear relay operators,
>>
>> I just wanted to let you know that RIPE has announced funding for The
>> Tor Project to improve IPv6 support on relays. (RIPE is the European
>> internet infrastructure organisation.)
>>
>> https://www.ripe.net/support/cpf/funding-recipients-2019
>>
>> We'll have more details early in 2020, when we've worked out an
>> implementation plan and a start time.
>>
>> Thanks for your patience with our current IPv6 support. And thanks
>> to all those volunteer coders who have worked hard to get us this far.
>>
>> T
>>
>> --
>> teor
>> --
>>
>>
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


smime.p7s
Description: S/MIME Cryptographic Signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] dew questions about Tor-relay

2018-05-03 Thread Jonathan Sélea
I suggest you actually read the Docs, all the answers is there.

---
Jonathan Sélea 

PGP Key: 0x8B35B3C894B964DD
Fingerprint: 4AF2 10DE 996B 673C 0FD8  AFA0 8B35 B3C8 94B9 64DD 
https://jonathanselea.se 

On 2018-05-03 15:37, dave` dave wrote:

> what is SocksPort, Controlsocket and Exitpolicy and Exitpolicy reject ip 
> address or :*: is in my "torrc" file.
> 
> can i set in my "torrc" file what ip i dont want/want to connect me? 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Let's increase the amount of exit relays doing DNSSEC validation

2018-04-15 Thread Jonathan Sélea
Great initiative!
Personally I would also see some sort of "DANE" for Tor-relays in the
future too, but that is a request for another thread.

/ Jonathan
> On 12.04.18 13:05, Alexander Dietrich wrote:
>
>> Just to be safe, you could also check the rest of the dig output and
>> /etc/resolv.conf (or relevant resolver configuration on your system)
>> to make sure your BIND is being used.
> I have seen hosters where /etc/resolv.conf is overwritten whenever the
> system reboots, and in these cases I used the following:
>
>   # Add this to /etc/tor/torrc
>   ServerDNSResolvConfFile /etc/tor/resolv.conf
>
>   # /etc/tor/resolv.conf
>   nameserver 127.0.0.1
>   # IPv6 alternative
>   #nameserver ::1
>
> -Ralph
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays




smime.p7s
Description: S/MIME-kryptografisk signatur
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays