On January 2, 2015 6:45:30 PM EST, 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. Reduced number of HSDir's (Sebastian Urbach)
2. Re: Reduced number of HSDir's (Austin Bentley)
3. Re: Reduced number of HSDir's (Kura)
4. Re: Reduced number of
HSDir's (Sebastian G. <bastik.tor>)
5. Help - My relay consensus has been stripped back to 20
(bigbudtor@xxxxxxxxxxxxx)
6. Re: Help - My relay consensus has been stripped back to 20 (s7r)
| From: | Sebastian Urbach |
|---|
| To: | tor-relays@xxxxxxxxxxxxxxxxxxxx |
|---|
| Sent: | Fri Jan 02 12:25:06 EST 2015 |
|---|
| Subject: | [tor-relays] Reduced number of HSDir's |
|---|
Hi,
https://metrics.torproject.org shows a big nose dive recently regarding the
number of HSDir's. Did i miss anything relevant in the last days ? That
seem to be the reason why i see increasing download numbers on my system.
Thanks for any lind of info.
--
Sincerely yours / SincÃres salutations
Sebastian Urbach
Definition of Tor:
10% luck, 20% skill, 15% concentrated
power of will, 5% pleasure, 50% pain and
100% reason to remember the name!
| From: | Austin Bentley |
|---|
| To: | tor-relays@xxxxxxxxxxxxxxxxxxxx |
|---|
| Sent: | Fri Jan 02 13:29:33 EST 2015 |
|---|
| Subject: | Re: [tor-relays] Reduced number of HSDir's |
|---|
No clue. I wonder if there's some backlash from a anti-attack mechanism of some sort? There was a few attempted attacks against the Tor network, but it wasn't anything worth discussing. Check out the post on the 31st from
blog.torproject.org.
| From: | Kura |
|---|
| To: | tor-relays@xxxxxxxxxxxxxxxxxxxx |
|---|
| Sent: | Fri Jan 02 13:47:51 EST 2015 |
|---|
| Subject: | Re: [tor-relays] Reduced number of HSDir's |
|---|
I think something must have happened, I restarted half a dozen or so of my relays over a week ago and none of them have been given the HSDir flag, which if I remember rightly is a 21 hour flag? I may be mistaken but, I would have expected that flag to be back with over a week of uptime.
On 02/01/2015 18:30:00, Austin Bentley <ab6d9@xxxxxxx> wrote:
No clue. I wonder if there's some backlash from a anti-attack mechanism of some sort? There was a few attempted attacks against the Tor network, but it wasn't anything worth discussing. Check out the post on the 31st from
blog.torproject.org.
| From: | "Sebastian G. " |
|---|
| To: | tor-relays@xxxxxxxxxxxxxxxxxxxx |
|---|
| Sent: | Fri Jan 02 14:51:26 EST 2015 |
|---|
| Subject: | Re: [tor-relays] Reduced number of HSDir's |
|---|
02.01.2015, 19:47 Kura:
I think something must have happened, I restarted half a dozen or so
of my relays over a week ago and none of them have been given the
HSDir flag, which if I remember rightly is a 21 hour flag? I may be
mistaken but, I would have expected that flag to be back with over a
week of uptime.
It used to be a 25 hour flag. 1 day plus an additional hour.
I think (yes, that says I don't know) the period being longer than 24
hours had something to do with an attack to get relays under adversary
control in the right position to become a HSDir for some
hidden-services. If one pays for a relays by days an additional hour is
an additional day for an attacker.
I may have missed something, but maybe it was raised.
I do remember that changes to Guards took place, like requiring them to
have more bandwidth and to reducing the number of Guards clients would
use. This was due to research.
Regards,
Sebastian
| From: | bigbudtor@xxxxxxxxxxxxx |
|---|
| To: | tor-relays@xxxxxxxxxxxxxxxxxxxx |
|---|
| Sent: | Fri Jan 02 18:28:48 EST 2015 |
|---|
| Subject: | [tor-relays] Help - My relay consensus has been stripped back to 20 |
|---|
On the 29th December one of our relays, bigbud (6911888F83565892FE23F1B03EB501D80E1E8780) which had a consensus of 630+ and had been running for nearly 18 months (100 days uptime running 2.5.8) suddenly started receiving much less traffic.
I have seen a gradual reduction in traffic over the course of the last year but on the 29th the drop off was very significant and I saw in Atlas that the consensus is dropped to 20. When I look at the consensus files
it shows that bigbud has a consensus of 20 and that Unmeasured was set to 1.
Any ideas please? I upgraded Tor to 2.5.10 after I noticed the consensus drop. Is this something to do with the Lizard new relay flood or something or is there an actual problem with the relay?
On a related note the relay lost guard status too a few months ago and I couldn't see why that would be.
| From: | s7r |
|---|
| To: | tor-relays@xxxxxxxxxxxxxxxxxxxx |
|---|
| Sent: | Fri Jan 02 18:39:52 EST 2015 |
|---|
| Subject: | Re: [tor-relays] Help - My relay consensus has been stripped
back to 20 |
|---|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This was reported yesterday 01.01.2015 in IRC too, for this relay:
3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
The same it was pushing good amounts of traffic and the consensus
weight dropped to 20 with no modifications made to the Tor config file
or anything. You are the 3rd person who reports this, seams like worth
investigating further.
I can see both of them are exits, but doubt this has anything to do
with it.
Could it be a measurement problem from the bandwidth authorities? Why
would it happen only to very few relays in this case?
On 1/3/2015 1:28 AM, bigbudtor@xxxxxxxxxxxxx wrote:
On the 29th December one of our relays, bigbud
(6911888F83565892FE23F1B03EB501D80E1E8780) which had a consensus of
630+ and had been running for nearly 18 months (100 days uptime
running 2.5.8) suddenly started receiving much less traffic.
I have seen a gradual reduction in traffic over the course of the
last year but on the 29th the drop off was very significant and I
saw in Atlas that the consensus is dropped to 20. When I look at
the consensus files it shows that bigbud has a consensus of 20 and
that Unmeasured was set to 1.
Any ideas please? I upgraded Tor to 2.5.10 after I noticed the
consensus drop. Is this something to do with the Lizard new relay
flood or something or is there an actual problem with the relay?
On a related note the relay lost guard status too a few months ago
and I couldn't see why that would be.
tor-relays mailing
list tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUpyxIAAoJEIN/pSyBJlsRB6MH+wWzDQPlhf+H4KWkoX9J6jhc
GQbL3+YmmZP1Eh941hnE6zaHpk5OUZiDarovBxSdL0FPEyHWlvLJIsFR6VXmfq2s
RB4hId21mKR5HQLNy/at6KP4Xs7dv3Qyid/KCZK3qH82HtJ9Yt9lA6yNTT8uLWmV
zIr1SKAMltBiIVrBWZaNGtqy5NVrGiF3yx2VYuHT7ZORL1l8BVjvG2I9d+/n2n7r
3RdEUKXSeFp/UnLlN5M9ZhHEdQLkioKfUisnkHdPKu7LTvWlVIONCm0t5lHo62xh
MUmbBP+lrWMfmQE8sJaTgmlJKq26Gb+JtG7uXV8k+XOfDokQygnFclJwZtUnKrQ=
=9kZo
-----END PGP SIGNATURE-----
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays