-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/01/15 19:02, Patrick Scharmer wrote:
> Hi,
>
> I’ve been running a bridge for over a year and noticed recently
> that the fingerprint shown in ARM (and that actually works when
> connecting to the bridge) differs from the fingerprint displayed
>
Update: generation of the http://nosur.com/consensus.txt list has
completed now, and contains 3683 relays that exist half a year or more.
Again the relays at the top of the list show the sharp drop in consensus
weight end of december and a short spike around January 6th.
_
FWIW, in my router I've just DMZ'd the static IP of my box (runs Mint 17) and bound the MAC to the IP - and have the firewall tight, plus some other hardening. Unless the cable goes down, all is smooth. Just changed my router and updated the firmware (TP-Link) with the same settings and only l
Try using a different port. Most Inc's block 80 and 443 to prevent people
running servers on home lines.
---
GPG/PGP Fingerprint
E129 722B A512 105C E8BE
4705 8046 EA48 2C82 1339
https://arlen.io/key
On Jan 18, 2015 5:26 PM, "Kurt Besig" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
On January 18, 2015 11:26:47 PM Kurt Besig wrote:
Hi,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been running a middle relay for nine months with great success,
however yesterday my ISP, TWC, upgraded my cable modem and everything
went south. Then unfortunately there was a firmware up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been running a middle relay for nine months with great success,
however yesterday my ISP, TWC, upgraded my cable modem and everything
went south. Then unfortunately there was a firmware upgrade for my
Asus RT-N66U router. Perfect storm, now My rel
Indeed, as Nicholas pointed out, this happened to many relays!
Using the onionoo database I am calculating the average consensus weight
during 18-25 october 2014, and the average consensus weight during 11-18
january 2015 of all relays that exist longer than half a year. Below is
the top 20 of rel
18.01.2015, 19:02 Patrick Scharmer:
> Hi,
Hi,
> I’ve been running a bridge for over a year and noticed recently that
> the fingerprint shown in ARM (and that actually works when connecting
> to the bridge) differs from the fingerprint displayed for my bridge
> on both Atlas and Globe. Any thought
Hi,
I’ve been running a bridge for over a year and noticed recently that the
fingerprint shown in ARM (and that actually works when connecting to the
bridge) differs from the fingerprint displayed for my bridge on both Atlas and
Globe. Any thoughts on why this would happen and how to fix it? I’
There is a similar issue with some other relays:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
https://atlas.torproject.org/#details/6911888F83565892FE23F1B03EB501D80E1E8780
There was a thread about it but nobody found out why
https://lists.torproject.org/pipermai
Hello,
You are not alone with this issue (
https://lists.torproject.org/pipermail/tor-relays/2015-January/006055.html
). The weirdest part is, that consensus is fixed to exactly 20 and on
Jan 06, on both nodes yours and mine the weight spiked up for a short
amount and then dropped back to 20.
All,
In December consensus weight of both my "nosurveillance" Tor exits dropped:
https://atlas.torproject.org/#details/7C3AE76BB9E9E6E4F2AE9270FD824DF54A944127
https://atlas.torproject.org/#details/E6D740ABFFAAAD8052EDF95B2C8DC4059763F365
I assumed this to be related to the directory authorities
The 'Named' flag is no longer assigned to relays.
Tom
webmaster schreef op 18/01/15 om 12:56:
Hello people out there,
whats the actually procedure to get a NAMED Flag?
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.t
Hello people out there,
whats the actually procedure to get a NAMED Flag?
--
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.17 (MingW32)
mQENBFHMmT8BCAC0smvU7Bq1ABxAhvBRn7d4ekkk95aCE4TTQo4wy1z/rGLhQfdt
dhiD+Vy61vGrsdK3ei5sW6rBvX2m8+YmBi+8AAgSiZmS0JM3Zz3cmTi5oh0D/yM8
4aDj7wQYfJyzSmYN
14 matches
Mail list logo
