On Fri, Aug 25, 2017 at 11:43:10AM +1000, teor wrote:
> > A new DFRI7 will appear on the same address and port within a couple of
> > days. Should I simply update fallback_dirs.inc?
>
> No need to do anything right away!
Will it be bad to have a new relay (with a new key), on the same IP:port
as
> On 25 Aug 2017, at 09:23, Linus Nordberg wrote:
>
> Hi teor,
>
> Fallback directory mirror DFRI7 [0] is down, due to multiple disk
> krashes, since about 30h and will not come alive with the same key.
>
> [0] 171.25.193.131:80 orport=443
Hi teor,
Fallback directory mirror DFRI7 [0] is down, due to multiple disk
krashes, since about 30h and will not come alive with the same key.
[0] 171.25.193.131:80 orport=443 id=79861CF8522FC637EF046F7688F5289E49D94576
A new DFRI7 will appear on the same address and port within a couple of
On Thu, Aug 24, 2017 at 11:42:23AM -0700, Kurt Besig wrote:
> While using apt-get to update my tor relay to a 'recommended' version I
> keep encountering this error:
>
> W: An error occurred during the signature verification. The repository
> is not updated and the previous index files will be
I have no say in how/when your relay can be reinstated. But, before
you resume any such research from any relay you should consult the Tor
Research Safety Board guidelines and then submit to them a request for
advice about the research you wish to do.
While using apt-get to update my tor relay to a 'recommended' version I
keep encountering this error:
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used. GPG error:
http://deb.torproject.org trusty InRelease: The
David,
My relay was harvesting .onion addresses and I apologize if that breaks any
rule or ethical guideline.
I'm a Junior Researcher at the Laboratory of Security and Cryptography at
University of Campinas. We were conducting some research on malicious
Hidden Services to study their behavior
On 24 Aug (12:11:47), Marcus Danilo Leite Rodrigues wrote:
> Hello.
>
> I was running a Tor Relay for the past month (fingerprint
> 71BEBB61D0D35234D57087D035F12971FA315168)
> at my university and it seems that it got banned somehow. I got messages on
> my log like the following:
>
> http status
Hello.
I was running a Tor Relay for the past month (fingerprint
71BEBB61D0D35234D57087D035F12971FA315168)
at my university and it seems that it got banned somehow. I got messages on
my log like the following:
http status 400 ("Fingerprint is marked rejected -- please contact us?")
response from
Hi,
On Wed, Aug 23, 2017 at 5:29 PM, Paul Templeton wrote:
> Thanx to all here on the list for input to earlier posts. Helped a lot.
>
> Question I have is there anywhere where you can get a block of IP address or
> lease as I'm in the process of getting a 10/10Mb SHDSL
One year ago we were trying the same in the Asia region with DigitalOcean. We
did not get a lot of traffic because of the few tor relays / bandwidth
authorities in Asia. At the moment your best chance in helping Tor with
bandwidth is buying a server in Europe or parts of the USA. If you have
OVH has this in AU
5.9
For security reasons, OVH reserves the right to proceed with the immediate
suspension without
notice, of any Server on which there is a public service Proxy, IRC, VPN or TOR
which is available free
of charge or for a fee, and for which OVH has knowledge of its
12 matches
Mail list logo