Hi,
I just opened a ticket.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have checked the whois records for the IP addresses of the outdated
relays which you earlier advised and found their providers. Opened
support requests and sent them a message.
Records were as follows:
93.174.90.30 su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have checked the whois records for the IP addresses of the outdated
relays which you earlier advised and found their providers. Opened
support requests and sent them a message.
Records were as follows:
93.174.90.30 supp...@ecatel.info n...@ecatel.in
That's great news Dan, keep us posted!
Chris
On 18 Sep 2014 21:40, "Dan Hanley" wrote:
>
>> I have just received a slightly more positive reply:
>
> "At present, our GeoIP data provider classes Tor nodes as proxies,
> regardless of whether or not they're an exit node. We understand that there
>
Hi all,
I've just reported this same issue this week, no reply yet.
I can still watch catch up BBC TV through my sky box though.
On 18 Sep 2014 21:40, "Dan Hanley" wrote:
>
>> I have just received a slightly more positive reply:
>
> "At present, our GeoIP data provider classes Tor nodes as prox
(if you are on the CC list of this email you are probably one of the tor
relay operators running one of the 10 fastest vulnerable [CVE-2014-5117]
relays on the tor network. Please upgrade your tor relay)
> The tor network is currently at 64% of the bandwidth being served by
> relays running a reco
>
>
> I have just received a slightly more positive reply:
"At present, our GeoIP data provider classes Tor nodes as proxies,
regardless of whether or not they're an exit node. We understand that there
is room for improvement in this model, since non-exit relays do not present
traffic on behalf of
>> Are these torservers' relays and is blutmagie showing their current
>> version? (not updated yet):
>
> Two boxes weren't updated correctly. The
> rest of the relays aren't from us, even though they show our contact
> info
Hi Moritz,
your answer was not very specific.
Is anonymizer1.torserver
Hi,
I also found a lot of the mentioned log entries. The comment from Arma
within the ticket is just right "Bonus points for using the name in the NSA
document"
Rofl :-)
--
Mit freundlichen Grüssen / Sincerely yours
Sebastian Urbach
-
Definition of TO
Hi,
> Now, I have checked the FAQs but didn't found any information where to
> report this, so I hope you can help me out.
>
> Thank you already and kind regards
it seems https://trac.torproject.org/projects/tor/ticket/12808 is the
place to go - the relay you mentioned was added by arma a few mi
Hi,
If there is still not enough bridge capacity available after a few people
already offered their help, i would be able to help with 400 Mbit (no
traffic limit).
--
Mit freundlichen Grüssen / Sincerely yours
Sebastian Urbach
-
Definition of TOR:
10%
Hi there
My relay logged the following warning this morning:
Sep 18 04:52:58.387 [Warning] Received an inbound RELAY_EARLY cell on
circuit 2147511747. Closing circuit. Please report this event, along
with the following message.
Sep 18 04:52:58.388 [Warning] upstream=85.159.214.57:9003
Now, I hav
I can also offer hosting, either EU or US. Please let me know, if I can be
helpful.
--SiNA
On Sep 18, 2014 3:14 AM, "Moritz Bartl" wrote:
> On 09/18/2014 04:51 AM, Mike Perry wrote:
> > Forwarded from tor-dev to here, in case any relay operators missed this:
> >
> > - Forwarded message from
On 09/18/2014 04:51 AM, Mike Perry wrote:
> Forwarded from tor-dev to here, in case any relay operators missed this:
>
> - Forwarded message from David Fifield -
For the sake of transparency, we are about to get a new machine in
Europe with OVH (~500 Mbit/s) that we won't use for Tor exi
On Wed, 17 Sep 2014 19:40:02 +, Paritesh Boyeyoko wrote:
...
> The actual connection is fast enough to not suffer real latency issues, it's
> just the relay doing the throttling
> - do you think throttling to 0.5Mbit/s or 1Mbit/s will create issues of high
> latency?
I've set the advertized
14 matches
Mail list logo
