> On 5 Aug 2015, at 05:52 , starlight.201...@binnacle.cx wrote:
>
>> At Tue Aug 4 11:22:22 UTC 2015 by Olaf Selke olaf DOT selke at blutmagie DOT
>> de
>>
>> by the way... I will probably shut down blutmagie
>> tor network status in September this year cause
>> the data center has terminated th
>At Tue Aug 4 11:22:22 UTC 2015 by Olaf Selke olaf DOT selke at blutmagie DOT de
>
>by the way... I will probably shut down blutmagie
>tor network status in September this year cause
>the data center has terminated the contract
>housing my servers 10/31/15.
Could you make your modified Torstatus c
Problem wit 0.2.7.2 is fixed. . .thank you Olaf!
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Am 04.08.2015 um 01:23 schrieb starlight.201...@binnacle.cx:
At 16:10 8/3/2015 +0200, you wrote:
debugging the old Blutmagie Perl scripts I found
all routers like splitDNA running Tor 0.2.7.2
sending two hash values in the extra-info-digest.
The second entry is a new 256-bit digest
that will e
At 16:10 8/3/2015 +0200, you wrote:
>debugging the old Blutmagie Perl scripts I found
>all routers like splitDNA running Tor 0.2.7.2
>sending two hash values in the extra-info-digest.
The second entry is a new 256-bit digest
that will eventually replace the current
160-bit digest and can be ignore
Hi Olaf,
The new ed25519 elliptic curve relay
identity certificate now occupies the top
of the extra-info document. The script
should be able to handle the elements
appearing in any order. Since the
script is written in perl this should
be an easy fix to search/match out the
read-history and wr
> debugging the old Blutmagie Perl scripts I found all routers like
> splitDNA running Tor 0.2.7.2 sending two hash values in the
> extra-info-digest. I suppose this isn't expected by the script parsing
> the data.
>
> GETINFO desc/name/splitDNA
> 250+desc/name/splitDNA=
> router splitDNA 62.210
Am 02.08.2015 um 17:39 schrieb starlight.201...@binnacle.cx:
FYI list
https: // torstatus DOT blutmagie DOT de
is registering relays running 0.2.7.2 as
having zero bandwidth.
I believe this is because the
write-history
read-history
lines in
extra-info
have moved from the top do
FYI list
https: // torstatus DOT blutmagie DOT de
is registering relays running 0.2.7.2 as
having zero bandwidth.
I believe this is because the
write-history
read-history
lines in
extra-info
have moved from the top down to the
middle of the document.
Many super-fast relays running
