that's designed to be secure even if
users aren't directly connected to their network entry points.
Can you tell us what you're trying to achieve for users by centralising
Tor services like this?
(And what services you intend to provide?)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP
ust using the
consensus: it only contains ORPort/DirPort IP addresses.
And Exits are free to use another IP as their OutboundBindAddress, so
some of the Tor exit lists check by actually making a connection
through the Exit.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90
ng. I'm running
> 3.2.0-121-generic-pae GNU/Linux on Ubuntu 12.04 (precise).
If you're on Ubuntu (or Debian) you can get the latest packages using
these instructions:
https://www.torproject.org/docs/debian.html.en
T
--
Tim Wilson-Brown (teor)
teor2345 at gm
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.torprojec
loped countries.)
>>
>
> *citation needed
Just compare the MIT IPv4 address allocations to those for many Asian
countries. [original research]
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:e
n't know if it would be
> preferable for someone more knowledgeable, or with more access to tor
> infrastructure, to be conversing with them. (e.g. teor)
>
> I assume some people will say this isn't even worth the effort; it's not
> like it's hard to just ignore those reports.
an IP changes.
>
> There are certainly ways around this (I could have a script populate torrc
> based upon DNS, for example) but it would make my life easier if I didn't
> have to.
>
> Thanks
>
>
> On 6 February 2017 at 23:10, teor <teor2...@gmail.com> wrote
rivate addresses, the easiest way to do this is to set:
TestingTorNetwork 1
This also changes some other torrc options: read the man page for details.
Tim
> On 6 February 2017 at 23:10, teor <teor2...@gmail.com> wrote:
>
> > On 7 Feb 2017, at 03:31, Andrew Smith <m...@andrewm
> On 8 Feb 2017, at 00:07, t...@afo-tm.org wrote:
>
> On 06.02.17 09:25, nusenu wrote:
>> The first release with the fix for [1] was in 0.3.0.3-alpha [2].
>> So if you run an IPv6 exit, upgrading to 0.3.0.3-alpha potentially
>> increases the tor network's IPv6 exit
;Address" torrc option takes a hostname, as do some other options
(I think the HiddenServicePort target is another.)
Thanks for the bug report, we'll fix the man page:
https://trac.torproject.org/projects/tor/ticket/21405
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail d
Is this (another ipv6) bug/issue in Tor or just expected ?
Automatic client IPv6 is a feature that has not been implemented yet.
But we need relays to have IPv6 ORPorts before it will work.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29
read this thread:
https://lists.torproject.org/pipermail/tor-relays/2017-January/011826.html
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: te
#n565
https://trac.torproject.org/projects/tor/ticket/21357
> As an aside, I just noticed there's a typo in the spec there at line 2294 --
> it reads"iff" instead of "if".
"iif" is shorthand for "if and only if".
T
--
Tim Wilson-Brown (teor)
teor2345 at
| starfish | tor-rel...@coldhak.ca| NULL |
>> | snowfall | tor-rel...@coldhak.ca| NULL |
>> | prawksi | tor-rel...@coldhak.ca| NULL |
>> | ogopogo | tor-rel...@coldhak.ca| NULL |
>> | tordiene | t...@die.net
> On 31 Jan 2017, at 10:51, nusenu <nus...@openmailbox.org> wrote:
>
> teor:
>> Here are the log entries I'd like to see:
>
> Does tor log any warning if IPv6Exit is set to 1 and the resulting
> descriptor will not contain any ipv6-policy line?
>
> If that i
> On 31 Jan 2017, at 05:13, nusenu <nus...@openmailbox.org> wrote:
>
> tldr: would you send me your torrc if you aim to route IPv6 exit traffic
> and are in the list at the bottom with the third colmn set to NULL?
>
> teor:
>> Either that, or there is a bug in Tor
> dependent on anything except ExitPolicy and IPv6Exit.
>>
>> Are there any log entries relating to IPv6 or exit policies?
>
> See above
Your relay still does not exit to IPv6.
This looks like it might be a tor bug, we're looking into it.
T
--
Tim Wilson-Brown (teor)
> On 30 Jan 2017, at 14:35, gustavo panizzo (gfa) <g...@zumbi.com.ar> wrote:
>
> On Mon, Jan 30, 2017 at 12:03:40PM +1100, teor wrote:
>
>> Hi,
>>
>> Please send us your actual torrc:
>
> that's my actual torrc, I've only edited HashedControl
t tor network.
For more information, please feel free to search the list archives.
(This question is asked reasonably often.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgs
MPP, XMPP SSL
> ExitPolicy accept *:5228 # Android Market
> ExitPolicy accept *:9418 # git
> ExitPolicy accept *:11371 # OpenPGP hkp
> ExitPolicy accept *:64738 # Mumble
> ExitPolicy reject *:* # nothing else is allowed
T
--
Tim Wilson-Brown (teor)
teor2345
ully, when exits upgrade to a tor version with these patches,
clients will connect to one exit, be told the IPv6 address, and then
connect to an exit that supports IPv6.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekm
they punish their users by refusing to swap packets with each
other.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
-
rg
(dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:80... connected.
HTTP request sent, awaiting response... 302 Found
...
dist.torproject.org works over IPv6 via a US Hurricane Electric tunnel,
and from OVH in France and Canada, so I'd check with your provider.
T
--
Tim Wilson-Brow
d if you don't set the IPv6Traffic on the SOCKSPort, you will never
connect to a remote IPv6 address.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
> On 19 Jan 2017, at 13:46, Geoff Down <geoffd...@fastmail.net> wrote:
>
> On Thu, Jan 19, 2017, at 02:33 AM, teor wrote:
>>
>>> On 19 Jan 2017, at 13:30, Geoff Down <geoffd...@fastmail.net> wrote:
>
>>> Then a HUP produced the same sequence (but
> On 19 Jan 2017, at 13:30, Geoff Down <geoffd...@fastmail.net> wrote:
>
>
> On Thu, Jan 19, 2017, at 01:14 AM, teor wrote:
>>
>>> On 19 Jan 2017, at 12:00, Geoff Down <geoffd...@fastmail.net> wrote:
>>> Jan 19 00:47:42.000 [notice] Tor 0.2.9.8
example, do you see something like:
Preparing managed proxy '%s' for restart.
(If so, this could be a bug in proxy_prepare_for_restart().)
Nothing changed for managed proxy '%s' after HUP: not restarting.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 9
TorWorld.org | LOLHillary |1 | NULL |
>> | e [AT] torworld.org | Cajun |0 | NULL |
>> | e [at] torworld.org | Gigi |1 | NULL |
>> | e...@torworld.org | SurfingAOL |1 | NULL |
>> +-
>>> tor-relays mailing list
>>> tor-relays@lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>>
>>
>> ___
>> tor-relay
it is refusing valid requests.
Is there a test for OpenDNS 'Malicious URL' filtering?
> (PS having a .onion contact address doesn't work, I think)
necto.onion is not a valid onion service: it does not have enough
characters.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855
idn't work. This can happen for a few different reasons.
> Do I need to reduce the number of connection to the relay or could I
> ignore this message?
Check the other warnings/notices near this warning.
If there aren't any, then there's no problem.
T
--
Tim Wilson-Brown (teor)
teor2345 at
> On 3 Jan 2017, at 17:38, Rana <ranaventu...@gmail.com> wrote:
>
> @teor
>> I think you are talking about a different network, which is not Tor as
> currently designed, implemented, and deployed.
>> In particular, how do you get decent throughput, reliability,
> On Tue, Jan 3, 2017 at 12:13 AM, teor <teor2...@gmail.com> wrote:
>
> > On 27 Dec 2016, at 03:47, Gage Parrott <gcparr...@gmail.com> wrote:
> >
> > Morning, everyone,
> >
> > I recently migrated my bridge relay over to a VM and everything seems t
g for?
UNKNOWN - 1F45542A24A61BF9408F1C05E0DCE4E29F2CBA11
TorWeatherHelper - 0F100F60C7A63BED90216052324D29B08CFCF797
Let me know, and I'll put them on the list.
Then we run a script before every release to pick the best ones.
Tim
> On Dec 4, 2016 5:45 AM, "teor" <teor2...@gmail.com> wrote:
>
> S
ise the
> directory port.
This is a feature: tor will only advertise the directory port if it is
sure it has spare traffic for directory requests.
This prioritises client traffic over directory requests.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094
process? Could adjust the torrc script for
> instance?
No, sorry, new relay details are only published in the tor consensus
every hour.
To reduce the 20 minute delay, you could write a script that issues a
SIGHUP (reconfigure) to tor when your address changes.
T
--
Tim Wilson-Brown (teor)
te
I missing?
Maybe the measurement system works, and your relay just can't sustain
high volumes of traffic (or large numbers of connections).
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 9
stion).
Perhaps some of us struggle to answer similar questions in the same
level of detail all the time. I know I do. It takes a lot of time to
elicit the level of detail needed to provide good answers.
Also when we're not polite, the discussion escalates into long threads
with few interes
s is the case, we'd *really* like to know what is
causing the issue. Please send more logs, at info-level if possible.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
the changes are large.
This might be because:
* the bandwidth rate is low,
* the connection speed is high compared to the bandwidth rate,
* the IP address changes, or
* the relay restarts, or
* perhaps some other reason.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A
is not Tor as
currently designed, implemented, and deployed.
In particular, how do you get decent throughput, reliability, and low-
latency out of tens of thousands of devices?
This is an open research problem, which the Tor design does not solve.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail d
> On 19 Dec. 2016, at 17:03, Ivan Markin <t...@riseup.net> wrote:
>
> teor:
>> It takes about a week for a TLS connection to close if there is
>> traffic on it, or a few minutes if there is no traffic:
> ...
>> Old TLS connections in tor are marked not to be u
.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
___
to
> On 19 Dec. 2016, at 05:56, root <t...@afo-tm.org> wrote:
>
> On 28.11.2016 00:01, teor wrote:
>> (I've rearranged your threads for clarity, please bottom-post in future.)
>>>> On Nov 27, 2016 11:59 AM, "root" <t...@afo-tm.org
>>>> <
or-relays] Tor relay from home - end of experiment?
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
___
> On 14 Dec. 2016, at 22:42, Andreas Krey <a.k...@gmx.de> wrote:
>
> On Wed, 14 Dec 2016 21:43:28 +, teor wrote:
> ...
>> The bwauth calculations do take latency into account, and they should:
>> if CPU usage or bandwidth are near their limit, the latency thr
ause of this, the median is of central importance in robust statistics, as
> it is the most resistant statistic, having a breakdown point of 50%: so long
> as no more than half the data are contaminated, the median will not give an
> arbitrarily large or small result.
T
--
Tim Wilson-Brown
an area which has a lot of low-latency
connections. If we shift that centroid, then the network will slow
down.
This is a problem that needs more research :-)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43
0: the relay itself reports that it is unable to sustain much tor
traffic.
GG2: it appears that the relay could handle more traffic, if you
increased the bandwidth rate and bandwidth burst.
I feel like I've given the same advice about ZG0 several times now, so
I'm going to leave that wit
> On 13 Dec. 2016, at 08:25, teor <teor2...@gmail.com> wrote:
>
>>
>> On 13 Dec. 2016, at 08:13, Rejo Zenger <r...@zenger.nl> wrote:
>>
>> Hey Tim,
>>
>> My relay now should be available on both IPv4 and IPv6. But, to be honest, I
>>
the logs
to make sure it says its guard is up.
Tim
> ++ 12/12/16 21:39 +1100 - teor:
>>
>>> On 12 Dec. 2016, at 19:15, Rejo Zenger <r...@zenger.nl> wrote:
>>>
>>> Hey!
>>>
>>> I do have IPv6 available, but I hadn't taken the time to a
one of the factors that feeds into the measured bandwidth.
Part of the calculation process for the consensus weight makes sure
that this feedback converges, rather than diverging.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rz
.
>
> Node: rejozenger, FP: AA0D167E03E298F9A8CD50F448B81FBD7FA80D56
>
> Kind regards,
> Rejo Zenger
Thanks, that would be great!
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygai
rproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
>
>
> --
> Patrick Derwael
> Rue de la fontaine, 3
> 4210 Burdinne
> G:0479.80.50.79
>
>
> ___
> tor
; tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.or
er interval
• read_history_values (list) -- bytes read during each interval
• write_history_end (datetime) -- end of the sampling interval
• write_history_interval (int) -- seconds per interval
• write_history_values
> On 12 Dec. 2016, at 05:08, Andrew Deason <adea...@dson.org> wrote:
>
> On Sun, 11 Dec 2016 23:45:42 +1100
> teor <teor2345-re5jqeeqqe8avxtiumw...@public.gmane.org> wrote:
>
>> One or more of your relays have been selected as fallback directory
>> mirr
saying that
it was constantly showing 100 kb/s.
Perhaps arm is displaying your maximum bandwidth over a certain time?
(I really don't now what bandwidth arm measures.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 09
t; in "Bps".
>>> Makes zero sense.
>
> Still doesn't. Why do Tor and Tor-related projects such as arm publish all
> these TOTALLY inconsiostent figures? If they want to confuse the adversaries
> I doubt that it worked, but they sure as hell were highly successful in
> confusing me
: teor <teor2...@gmail.com>
Subject: Call for Tor Fallback Directories
Date: 4 December 2016 at 21:44:39 AEDT
To: tor-relays@lists.torproject.org
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a
fallback directory mirror.[0]
These mirrors are hard
ts.torproject.org/pipermail/tor-relays/2016-November/010913.html
> https://lists.torproject.org/pipermail/tor-relays/2016-November/010928.html
> https://lists.torproject.org/pipermail/tor-relays/2016-November/010916.html
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4
r a connection from
your relay to itself.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: te
h!
You can't buy a t-shirt, but they are available by donation:
https://donate.torproject.org/
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp:
s work well, we would need bandwidth authorities in Africa
and Asia. Otherwise, those relays won't be used much.
(We're working on it - I hope!)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgs
l a
non-Linux OS).
For Tor client path selection, it is typically the vulnerable consensus
weight that matters, not the number of relays.
(Except in the case of HSDirs, where the hash ring is unweighted.)
Have you looked at the vulnerable consensus w
>
> From SanTOR
Hi,
Jon is distributing t-shirts and Christmas cheer this year.
Have you been naughty or nice?
And by the way, it's SanTor, not SanTOR (or SANTOR).
(And our trademark lawyers prefer onion jokes.)
:-)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A
viding an accurate list.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
__
rprint, so I'll do that. Thanks!
Yes, this is what people typically do. Thanks!
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
> On 7 Dec. 2016, at 11:38, Tobias Sachs <kni...@germancraft.net> wrote:
>
> Hey teor,
>
> my relay 5665A3904C89E22E971305EE8C1997BCA4123C69 is according to your log
> [4] black and whitelisted. But it is only in the whitelist from y
this time.
Thanks, I added your relay to the whitelist.
TorWeatherHelper - 0F100F60C7A63BED90216052324D29B08CFCF797
I'll run the script later in December that generates a list of relays for the
release.
Tim
>
> Thanks
>
> On Sun, Dec 4, 2016 at 5:44 AM, teor <teor2...@gmail.
ay is publicly listed in the tor consensus. If you want to
keep the details private, run a bridge relay.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygai
here and someone will fix it.
> On 12/06/2016 11:33 AM, teor wrote:
>>
>>> On 6 Dec. 2016, at 21:15, Sec INT <sec.i...@gmail.com> wrote:
>>>
>>> Hi
>>>
>>> Does anyone know a contact for updating the wiki page for good bad isps -
&
nd someone will fix it.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
_
;>>
>>> ___
>>> tor-relays mailing list
>>> tor-relays@lists.torproject.org
>>> https://lists.torproject.org/cgi-
means it can drop off the
network, or fail to keep its consensus up to date.
Please update, and try again.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor
this list.
I will respond to every reply I get.
But please give me at least 3 days to respond before checking again.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp:
s per user on your OS and distribution.
Tim
> -Original Message-
> From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf
> Of teor
> Sent: Sunday, December 04, 2016 11:42 PM
> To: tor-relays@lists.torproject.org
> Subject: Re: [tor-relays]
> On 5 Dec. 2016, at 02:55, Pascal Terjan <pter...@gmail.com> wrote:
>
> On 4 December 2016 at 14:20, teor <teor2...@gmail.com> wrote:
>>
>>> On 4 Dec. 2016, at 22:18, teor <teor2...@gmail.com> wrote:
>>>
>>>> On 4 Dec. 2016, at
elays-boun...@lists.torproject.org] On Behalf
> Of teor
> Sent: Sunday, December 04, 2016 11:34 PM
> To: tor-relays@lists.torproject.org
> Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
>
>
>> On 5 Dec. 2016, at 08:11, Rana <ranaventu...@g
riginal Message-
> From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf
> Of teor
> Sent: Sunday, December 04, 2016 11:07 PM
> To: tor-relays@lists.torproject.org
> Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
>
>
ng
trade-offs between these factors.
Using all available relay bandwidth is not a priority: we will happily
use less bandwidth to provide better latency or better security.
Tim
> -Original Message-
> From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behal
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.
ve
>>> this set?
>>>
>>>> In Germany, it's quite usual that you have a dynamic IP and unusual that
>>>> you have static IP. Not just a few relays are located in Germany. It's
>>>> not just a question of frustration of owners of dynamic IP rel
se
they then lose access to your bridge.
(Unless they ask the bridge authority for your new descriptor. I'm not
sure if that code works the way we want it to - I don't know how often
we test it.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D4
reasons I mentioned in my original
email.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
_
> On 4 Dec. 2016, at 22:18, teor <teor2...@gmail.com> wrote:
>
>> On 4 Dec. 2016, at 22:06, Pascal Terjan <pter...@gmail.com> wrote:
>>
>> On 4 December 2016 at 10:44, teor <teor2...@gmail.com> wrote:
>>> ...
>>>
>>>
> On 4 Dec. 2016, at 22:06, Pascal Terjan <pter...@gmail.com> wrote:
>
> On 4 December 2016 at 10:44, teor <teor2...@gmail.com> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Dear Tor Relay Operator,
>>
>> Your relay
://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors
[6]:
https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/updateFallbackDirs.py
[7]: https://trac.torproject.org/projects/tor/ticket/18828
T
- --
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP
arted, if you'd still like specific
advice after reading those threads, feel free to let us know your
relay's fingerprint.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D
server for tor traffic,
at least on Linux servers.
For more details, read:
https://gitweb.torproject.org/chutney.git/tree/README#n59
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet
> On 30 Nov. 2016, at 02:18, Zack Weinberg <za...@cmu.edu> wrote:
>
> On Sun, Nov 27, 2016 at 6:01 PM, teor <teor2...@gmail.com> wrote:
>>
>> If IPv6 penetration among Tor relay ISPs/ASs is as high as you say, why
>> do only:
>>
>> 7.6% (
> On 28 Nov. 2016, at 10:01, teor <teor2...@gmail.com> wrote:
>
>>> All this new fancy ISPs that have FTTH and
>>> give you 500 MBit/s symmetric internet access have Carrier grade
>>> NAT because they were late to the Party and don't get IPv4 f
> On 29 Nov. 2016, at 18:44, Roman Mamedov <r...@romanrm.net> wrote:
>
> On Mon, 28 Nov 2016 10:01:03 +1100
> teor <teor2...@gmail.com> wrote:
>
>> (I've rearranged your threads for clarity, please bottom-post in future.)
>>
>>>>
FTTH ISP that offer 200+ MBit/s symmetric and only public IPv6
> would gain more Consensus Weight than all Relays we would have lost due to
> that change together.
I think you're confusing ASs with IPv6 allocations and relays with
configured IPv6. They're very different things. And there's
very small packets?
(Interactive protocols like chat and SSH could be responsible.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
-
an IPv4 address to publish a descriptor.
A relay can also publish an IPv6 address it its descriptor.
Tim
>
> Cheers
> Lluís
>
>
> teor:
>>
>>> On 23 Nov. 2016, at 02:54, Ralph Seichter <tor-relays...@horus-it.de> wrote:
>>>
>>>
1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;gieselbusch.de.IN MX
;; ANSWER SECTION:
gieselbusch.de. 150 IN MX 5 smtpin.rzone.de.
;; ADDITIONAL SECTION:
smtpin.rzone.de.1724IN A 81.169.145.97
Tim
>
not believe the root certificate that signed the smtp.rzone.de
certificate.
In any case, it's nothing to do with Tor.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450
> D
>
> On 22.11.2016 00:28, Kevin Zvilt wrote:
> Seems my proxy is refusing all connections.
>
> On Tue, Nov 22, 2016 at 1:35 AM, Mirimir <miri...@riseup.net> wrote:
>
> On 11/21/2016 04:21 PM, Kevin Zvilt wrote:
> Kevin from Cairo, still trying to set up Tor a
> On 23 Nov. 2016, at 02:54, Ralph Seichter <tor-relays...@horus-it.de> wrote:
>
> On 22.11.16 03:33, teor wrote:
>
>>> ...
>
>>> ClientPreferIPv6DirPort 1
>>
>> This option was introduced and deprecated in the 0.2.8 alpha series,
601 - 700 of 995 matches
Mail list logo
