> On 22 Nov. 2016, at 14:07, diffusae <punasip...@t-online.de> wrote:
>
> Hi!
>
> On 22.11.2016 03:33, teor wrote:
>> 0.2.9 alpha
>
> Is it safe to use 0.2.9 alpha on relays
We think it is safe to use 0.2.9.5-alpha on relays.
But we could do with mor
> On 22 Nov. 2016, at 03:18, Ralph Seichter <tor-relays...@horus-it.de> wrote:
>
> On 21.11.2016 16:39, teor wrote:
>
>> Relays require an IPv4 address, because every relay in the Tor network
>> needs to be able to connect to every other relay. If some rela
v6 ORPort on your relays and bridges?
Exits can support client access to dual-stack and IPv6-only websites.
Do you set IPv6Exit on your exits?
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F
gt; I couldn't find if worth to run over IPv6 or not.
No, IPv6-only relays won't work.
Tor relays need to be able to connect to every other relay, and (at
least for the foreseeable future) all relays have an IPv4 address.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855
roject.org/windows/en-US/onion-services.html
Tim
>
> On Sat, Nov 19, 2016 at 1:21 AM, teor <teor2...@gmail.com> wrote:
>
> > On 19 Nov. 2016, at 09:52, Kevin Zvilt <kevinzv...@gmail.com> wrote:
> >
> > 11/18/2016 17:28:08 PM.600 [NOTICE] Bootstrapped 85%: Finishing
; DisableNetwork is set.
Hi,
Can you help us understand what the problem is?
You might need to use "Log info file info.log" or
"Log debug file debug.log" to get enough detail for us to help you.
T
--
Tim Wilson-Brown (teor)
teor234
e a separate
file and ServerDNSResolvConfFile.)
If your provider is that sensitive about DNS traffic, it might be
best to point your resolver at some other public DNS servers.
But please don't use Google, they see too much Tor DNS traffic alrea
BE23AE5
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
--
Tim Wilson-Brown (teor
packet.go
> statefile.go
>
> obfs4/transports/obfs4/framing:
> framing.go framing_test.go
>
> obfs4/transports/scramblesuit:
> base.go conn.go handshake_ticket.go handshake_uniformdh.go hkdf_expand.go
> ___
> tor-
o you have apparmor installed?
If so, what are the logs?
In any case, what does Tor try to do every 5 minutes?
(Look at the info or debug logs.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot
/ Nyx (the new name for arm).
https://trac.torproject.org/projects/tor/newticket
And please also log a ticket under Core Tor / Tor saying that we are
modifying Nickname from its default value, and writing it out again,
rather than modifying our idea of it internally.
https://trac.torproject.org/pro
> On 11 Nov. 2016, at 05:39, diffusae <punasip...@t-online.de> wrote:
>
> Hello,
>
> thanks for your help.
>
> On 10.11.2016 02:31, teor wrote:
>
>> No-one is working on it, as far as I know.
>
> All right, now I see. It's a "nice to have fea
> On 10 Nov. 2016, at 10:12, diffusae <punasip...@t-online.de> wrote:
>
> Hi!
>
> Thanks a lot for you reply.
>
> On 08.11.2016 22:56, teor wrote:
> ...
>
>> You want this one, which is not fixed:
>> https://trac.torproject.org/projects
rg/projects/tor/ticket/5940
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
--
___
f the available nodes
> * leading to higher network throughput
>
> Does that sound plausible?
The first two, yes, the last two, perhaps.
Maybe lower latency is more important than throughput?
But each bandwidth authority uses bandwidth that would otherwise be available
to clients. So th
> Nov 01 20:38:17.000 - 23232
>
> 140 times exactly 49 repeats in around 2 hours.
>
> Interesting is that there is no error about this 503 error in the log
> only my monitoring is aware of the issue.
>
> I hope you coul'd help me out with this issue.
Maybe you should turn your
reason for an ISP to change prefixes for IPv6, they should
have plenty of address space. Sounds like they're treating it just
like IPv4.)
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA
ing more bandwidth.
For your relay, this means increasing BandwidthRate and BandwidthBurst.
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
th is
approximately the same as
> the bandwidth measured by the bandwidth
> authorities.
>
> If you want to fix this, add more bandwidth.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 2
igned: your relay's observed maximum
bandwidth is almost identical to the bandwidth measured by the bandwidth
authorities.
If you want to fix this, add more bandwidth.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgs
haps we want to assume that new relays will have the network average
uptime. So any uptime that's better than average should improve your relay's
chances of getting the Guard flag.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricoch
m 1, and when you reach the mask number,
the IP range is all the possible combinations of all the remaining bits.
Tim
> On Nov 1, 2016 9:58 AM, "teor" <teor2...@gmail.com> wrote:
>
> > On 2 Nov. 2016, at 01:54, SuperSluether <supersluet...@gmail.co
t;> 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.tor
> On 1 Nov. 2016, at 23:12, Louie Cardone-Noott <l...@fastmail.net> wrote:
>
> On Tue, 1 Nov 2016, at 11:42 AM, teor wrote:
>>
>>> On 1 Nov. 2016, at 15:58, <ane...@tutanota.de> <ane...@tutanota.de> wrote:
>>>
>>> In order to cl
_
> 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:/
> No. Thats my problem too, around 90% of my abuse mails are bot related
> and you cant do anything about it.
If you know the destination IP address, and it's a bot Command & Control
server, you could block it. The problem is, many use mul
> On 27 Oct. 2016, at 00:32, D. S. Ljungmark <spi...@takeit.se> wrote:
>
> On tis, 2016-10-25 at 22:52 +1100, teor wrote:
>>>
>>> On 25 Oct. 2016, at 22:26, D.S. Ljungmark <ljungm...@modio.se>
>>> wrote:
>>>
>>> So, Now I
the list doesn't accept attachments :)
It turns them into links.
They work fine.
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgs
past 100-200Mbit? Is it just a
>>>>>>>>>>> waiting game?
>>>>>
>>>>> I'd say just run more instances if you still have resources left and
>>>>> want to contribute more bw.
>>>>> (obviously also your
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C85
d.
But you are still contributing to the network.
You could try renting a cheap server in a data centre.
Most of them offer static IP addresses.
Tim
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
rovider might be the
common factor.
Sorry we can't do much to help.
Tim
>
> Thanks again.
>
>
>
> On 10/15/2016 09:08 PM, teor wrote:
>>> On 14 Oct 2016, at 22:23, Tor User <toru...@lvwnet.com>
>>> wrote:
>>>
>>> I apologize f
t; more details?
> Might be.
>
> --
> Felix
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
--
Tim Wilson-Brown (teor)
teor234
if it's just FreeBSD, or just LibreSSL.
Maybe mention the bug number on tor-talk, so that poster can provide
more details?
Tim
>
> --
> Best regards, Felix
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> htt
and would avoid race conditions.
Of course, that doesn't change the resolver for the rest of your system.
Tim
>
> --
> Jesse
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cg
roject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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-bin/mailman/listinfo/tor-relays
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094
hit x twice to reload the values it only seems to refresh for the moment
> but when I restart it's back to the errors.
>
> Anyhelp would be greatly appreciated.
Tell us what you think the issue is, and what you've tried doing to fix it.
Then we can be more helpful.
T
--
Tim Wilson-Brown (teor)
Consequently, I have to
> keep an eye on /etc/resolv.conf to ensure that it always points to my
> Unbound instance. I take immediate action if this is not the case.
You might find ServerDNSResolvConfFile useful if you want to avoid using
the default system resolver file /etc/
speedtest.net upstream tests above 20 megabits/sec to
> different speedtest sites around eastern US "hubs" (atlanta, virginia, ie,
> places that have bandwidth). So I don't understand.
I would say "ask your provider", but I doubt they'll be sympathetic.
Perhaps finding anothe
of the official torproject onions are here:
https://onion.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: teor at torproject dot org
-
enable an IPv6 DirPort.
Tim
>
> Regards
>
>
> On 13.10.2016 01:46, teor wrote:
>>
>>> On 13 Oct 2016, at 06:07, diffusae <diffu...@yahoo.se> wrote:
>>>
>>> Hi!
>>>
>>> On 12.10.2016 07:18, Manny wrote:
>>>> Oh and since I'
ve
> commented out the obfs4 line for now.
>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
--
Tim Wilson-Brown (teor)
teor234
But if your priority is local network
censorship-evasion, then IPv6 might just work for you.
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
e report automated thresholds.
In my experience, the abuse complaints are auto-generated, and no-one
replies to my offer to block the site. So why not eliminate the
complaints? Then everyone will be happy. Except the bot-herders.
Tim
>
> Markus
>
>
> 2016-10-09 1:57 G
needed to work out if this is even feasible,
and, if it is, what rate limits should apply to what ports.
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
signatu
t; tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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
signature.asc
Descripti
and port if the remote
site wanted us to. We never received a reply.
What does OVH expect its Exit operators to do with complaints?
Should we have blocked each complaining IP address as soon as we received a
complaint?
Tim
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED
_
> 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.
en you need them.
When your relay publishes a descriptor, it will make more circuits as needed to
relay client traffic.
Tim
>
> On 03.10.2016 03:34, teor wrote:
>>> On 2 Oct 2016, at 17:17, Sheesh <she...@ip-static.eu>
>>> wrote:
>>>
>>> Thanks fo
ess can be used twice, once with an IPv4 address and once
with an IPv6 address. Outbound traffic on a non-exit relay is all IPv4,
and it will use the routing table if you don't use OutboundBindAddress.
Unless you have multiple IPv4 addresses, it won't make any difference.
T
--
Tim Wilson-Brown (teo
normal
> computer/console. When I run Tor myself it's from a different machine in
> order to use the Tor browser. All I want the mini to do is act as a relay,
> nothing more.
Here's how you can start a relay on OS X on boot:
https://trac.torproject.org/projects/tor/wiki/doc/MacRunOnB
aints…
T
>
> Markus
>
>
>
>
>
>
> 2016-09-30 23:33 GMT+02:00 teor <teor2...@gmail.com>:
>>
>>> On 30 Sep 2016, at 14:01, Green Dream <greendream...@gmail.com> wrote:
>>>
>>> Have you double-checked the ulimit was appl
s
> (if there are any other error or warning messages besides the one you
> already listed).
The debian packages should set the appropriate file descriptors for you.
How are you launching your tor services?
T
--
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D
you run a local, caching, DNS resolver?
That could be a bottleneck, as almost all of your observed bandwidth is based
on exit traffic.
The details are below:
> On 22 Sep 2016, at 03:58, D. S. Ljungmark <spi...@takeit.se> wrote:
>
> On tor, 2016-09-22 at 06:29 +1000, teor wrote:
>
't do very well on ipv6. )
You can run two tor instances per IPv4 address.
Alternately, if your relay fingerprint has had a particularly bad set of random
selections, you could try deleting the RSA and Ed25519 identity keys, and
starting again. This will reset your reputation on the network.
capacity anyway, slightly
more on Exits - this utilisation level helps keep latency low.)
Later versions have better multithreading and crypto optimisations - thanks for
keeping your relay up-to-date.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 9
ed to seek information.
>
> /scooby
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> ___
> tor-rel
s?
Also, have you tried searching the mailing list archives?
This question gets asked and answered at least once a month.
Tim
>
> //D.S.
>
> --
> 8362 CB14 98AD 11EF CEB6 FA81 FCC3 7674 449E 3CFC
>
> ___
> tor-relays mailing list
&
; tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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
st
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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
signature.asc
Desc
as before it
was restarted?
Are its ports open to all other relays?
Can it open connections to other relays, regardless of their ports?
Did you make any other config changes at the same time?
Tim
>
> Am 13.09.2016 um 10:37 schrieb teor:
>>> On 13 Sep 2016, at 18:05, jensm
_
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teo
___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk
will recover fairly quickly.
It's completely up to you - I just wanted to describe the security advantages
of a fresh start, versus the traffic advantages (or disadvantages) of keeping
the same relay keys.
Tim
>
> Paul
>
>
> Am 12.09.2016 um 03:53 schrieb teor:
>
>&g
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43
ackage manager (using something like dpkg-divert), or change the
--defaults-torrc path in your service manager (and if you're on Debian, that
file is in /lib/systemd/system, and so you'll need to do dpkg-divert on it).
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C
ely because they run out of a datacentre at a large provider, rather than
someone's home internet connection.
Tim
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
signature.asc
Des
>
> In that case, the specification hard-codes the probability of an exit
> taking on a non-exit role (Wgd, Wmd, and Wme) to 0.
>
It's also worth noting that Exits will serve directory documents and hidden
service descriptors, and act as introduction and rendezvous points, so your
est
__
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:
.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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
signature.asc
Description: Message signed wit
group dealing with Internet activities), and let them know about Tor and your
Exit relay. And let them know you don't keep any logs, and Tor can't identify
the end user anyway by design. That keeps them informed, and gives them someone
to contact if there are ever any concerns about your relay.
> On 4 Sep 2016, at 22:55, pa011 <pa...@web.de> wrote:
>
>
>
> Am 01.09.2016 um 05:39 schrieb teor:
>>
>>> On 1 Sep 2016, at 13:36, I <beatthebasta...@inbox.com> wrote:
>>>
>>> Did someone mention t-shirts?
>>>
>>&g
ng long-lived
connections.
Or perhaps other traffic on your connection competes with the Tor traffic, and
causes it to time out?
Tim
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
not multithreaded enough), and at least somewhat closer to not being
> practically idle. Can you launch 'top' and press '1' there to check?
>
> Also seems unclear why it didn't get the guard flag for so long, does your
> public IP address change from time to time? Or do you turn the rela
>
> --
> Finding information, passing it along. ～SuperSluether
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C8
ped due to any relay being over
capacity, this adds a significant delay, because of how Tor retransmits along
the entire path, not just the busy relay's hop.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 4
If you want one, please feel free to get in touch with him, I've CC'd him on
this email.
Tim
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
signature.asc
Description: Mes
n't listed in the
> ## main directory. Since there is no complete public list of them, even an
> ## ISP that filters connections to all the known Tor relays probably
> ## won't be able to block all the bridges. Also, websites won't treat you
> ## differently because they won't know you're running To
team in the loop, so that relay operators know who to contact if I'm away.
(Oh, and please let us know if you're getting *too much* email!)
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
the MaxMind GeoIP database, so upstream changes will automatically be
included in Atlas.
(I'm not sure what our update schedule is for Atlas.)
We're working on getting better AS information here:
https://trac.torproject.org/projects/tor/ticket/19437
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot co
world.
It's also ok to set up a bridge for your local tor clients, and have them
access the tor network through that bridge.
There's no need to run an exit relay locally.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricoch
- there are legal and ethical
consequences to traffic selection.
Tim
>
> the white rider
> (Het leuke van ... is
>
>
>
> the white rider
> (Het leuke van ... is
> On 18 aug. 2016, at 01:30, teor <teor2...@gmail.com> wrote:
>
>>
>&g
> On 18 Aug 2016, at 15:46, Andrew Deason <adea...@dson.org> wrote:
>
> On Wed, 17 Aug 2016 12:23:15 +1000
> teor <teor2345-re5jqeeqqe8avxtiumw...@public.gmane.org> wrote:
>
>> Has anyone checked if the logs on other resolvers (like unbound) have
>>
directory authorities up.
Tim
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
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
the same
issue?
Tim
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
signature.asc
Description: Message signed with OpenPGP using GPGMail
patched in some distributions.)
Tim
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
signature.asc
Description: Message signed with OpenPG
raise it to 300 too. So maybe this once changing
> /lib was actually ok :)
Hi weasel,
It looks like you changed it in
https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@.service
but not in:
https://gitweb.torproject.org/debian/tor.git/tree/debian/systemd/tor@default.service
I
> On 3 Aug 2016, at 10:29, teor <teor2...@gmail.com> wrote:
>
> Clients on 0.2.7.6 and earlier still use the IPv4 DirPort.
> (Tor Browser is still 0.2.7.6, and apps in general may take some time to
> upgrade.)
>
> Authorities on0.2.7.6 and earlier will only assi
ase enable IPv6 on your relay, if you can.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmmp: teor at torproject dot org
signature.asc
Description: Message signed with OpenPG
he 0.2.8 alpha series, and then
obsoleted in a subsequent alpha, because only clients use IPv6 for directory
fetches, and clients only use the IPv6 ORPort. There's no way to advertise an
IPv6 DirPort, and no reason for a relay to have one.)
Tim
Tim Wilson-Brown (teor)
teor2345 at gma
oject.org
>>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>>>
>>>> ___
>>>> tor-relays mailing list
>>>> tor-relays@lists.torproject.org
>>>> https
is not an exit.
Perhaps it was a (D)DoS attack, and the provider is confused about where it was
coming from?
Perhaps the server was used in a (D)DoS attack? (Does it serve DNS? Does that
DNS have large records?)
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43
tree/README.md#n87
>
> Kind regards
> Tor-node.net
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at
__
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
signa
> On 8 Jul 2016, at 09:48, Tim Wilson-Brown - teor <teor2...@gmail.com> wrote:
>
>
>> On 8 Jul 2016, at 09:41, nusenu <nus...@openmailbox.org> wrote:
>>
>> Hi Seongmin,
>>
>> out of curiosity I was wondering whether your so called tor "
___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet
e?
We're working on it, and it's called "next generation hidden services".
Until then, relays get banned for this behaviour.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
s
crypted beginner connections are made over the ORPort.
This means that in 0.2.8 clients no longer use any DirPort, and relays only use
the IPv4 DirPort.
IPv6 clients and bridge clients use the IPv6 ORPort.
In 0.2.7 and before, clients and relays only use the IPv4 DirPort.
IPv6 bridge clients use
for small changes before merging.
>
> Thanks,
> Iain.
>
> [1]: https://trac.torproject.org/projects/tor/ticket/5430
> [2]: https://trac.torproject.org/projects/tor/ticket/6787
> ___
> tor-dev mailing list
>
701 - 800 of 995 matches
Mail list logo
