quarter share and exits a half share. It is very difficult to run a
fast stable middle because as soon as you accomplish that it becomes
eligible for the guard flag and no longer gets used as a middle.
I could hardly have said the below better.
-Pascal
On 9/28/2014 8:03 AM, Sebastian Urbach wrote
It would be nice if Tor had an option to display the flags it was
compiled with.
-Pascal
On 10/26/2014 1:48 PM, Toralf Förster wrote:
On 10/26/2014 07:21 PM, Michael Kelly wrote:
0.2.5.9-rc (and later to 0.2.5.10).
Because there's no code change (except the version string itself) be
Why does this package:
send Tor SIGTERM instead of SIGINT (during yum update)?
lower "ulimit -n" to 32768?
-Pascal
On 10/27/2014 7:51 AM, Ondrej Mikle wrote:
Hi,
when switching RPMs from 0.2.4.x to 0.2.5.x branch I forgot to merge re-enabling
of Curve25519 (it was a historic artif
his? E.g. if a directory
authority detects an exit relay is in a location known to block access
to/MITM specific IPs/ports it automatically updates the exit policy for
that node in the directory to exclude them.
-Pascal
On 12/4/2014 8:55 AM, Vladimir Ivanov wrote:
hi.
Recently, github
ce then, but nickm states rather plainly that
microdescriptors do not support excluding specific IPs.
-Pascal
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
repos unexpectedly.
-Pascal
On 1/1/2015 2:58 PM, Sascha Siekmann wrote:
Hello,
Happy New Year, everone! I've been chasing this down here for the last hour or
so and I thought I might as well share it since others might also experience it.
I am running https://atlas.torproject.org/#s
their merchant account terminated if they get enough of them.
-Pascal
On 2/25/2015 12:35 PM, Speak Freely wrote:
This has cost me hundreds of dollars, as I foolishly decided to prepay
on an annual basis. None of the servers were older than 2 months. Some
were only a few weeks old
way, real world maybe 5-600mbps). As
your Tor nodes should not be talking to each other, only to Tor nodes
not in your family, you could easily put a separate cheap firewall in
front of each node rather than having one big firewall for everything.
-Pascal
On 7/26/2012 1:08 PM, Dennis Ljungmark
The Tor exit notice at
https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/tor-exit-notice.html
contains the word "server" exactly once. It should probably be changed
to "router" to match the rest of the document and avoid the common
assumption that servers
http://torstatus.blutmagie.de indicates that only 21.4% of Tor nodes are
exit nodes. Are we wasting this precious resource by running non-exit
traffic through these nodes?
-Pascal
___
tor-relays mailing list
tor-relays@lists.torproject.org
https
I run a Freenet node on my Tor servers with lots of disk space. Two of
them are publicly accessible:
https://freenet.us.to
https://mogxgdxb7xk26blk.onion
Tor uses lots of bandwidth & CPU while Freenet uses lots of disk space
so they complement each other nicely.
-Pascal
On 10/4/2013
Is there a document somewhere I can refer my ISP to showing that other
ISPs have decided to blackhole Irdeto/IP-Echelon complaints?
-Pascal
On 11/13/2013 4:50 PM, Moritz Bartl wrote:
Hi,
One of our ISPs has decided to simply blackhole all complaints
coming from Irdeto/IP-Echelon
On 20 May 2016 at 12:32, Dionysis Grigoropoulos wrote:
> On Fri, May 20, 2016 at 12:18:01PM +0100, Pascal Terjan wrote:
>> I haven't been able to access BA website from home for the last few weeks.
>>
>> I have failed to get any other answer on the phone that to try usi
For example
https://atlas.torproject.org/#details/20462CBA5DA4C2D963567D17D0B7249718114A68
says uptime is 12 days and current version is 0.2.6.10 but I upgraded
the machine and updated tor to 0.2.8.9 over a day ago:
# uptime
09:30:50 up 1 day, 8:32, 1 user, load average: 0.68, 0.81, 0.88
# ps
On 1 November 2016 at 10:16, Karsten Loesing wrote:
> Hi everyone,
>
> can you check once again?
>
> There was a problem with the data-collecting service that silently
> died on October 30 at around 23:00 UTC. I have been working on that
> problem for an hour or two, and it should be resolved by
On 15 November 2016 at 20:41, Arisbe wrote:
> One of my tor guard relays is a medium size VPS operating in the Czech
> Republic. It's been up and stable for several years. Several weeks ago I
> was notified that my VPS was a source of UDP DoS traffic. It was shut down.
> Logs showed no intrusio
On 4 December 2016 at 10:44, teor wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Dear Tor Relay Operator,
>
> Your relay(s) can help tor clients find the tor network by becoming a
> fallback directory mirror.[0]
>
> These mirrors are hard-coded into tor's source code, like the dire
On 4 December 2016 at 14:20, teor wrote:
>
>> On 4 Dec. 2016, at 22:18, teor wrote:
>>
>>> On 4 Dec. 2016, at 22:06, Pascal Terjan wrote:
>>>
>>> On 4 December 2016 at 10:44, teor wrote:
>>>> ...
>>>>
>>>> Your
On 4 Dec 2016 9:58 pm, "Rana" wrote:
That was exactly my point, thank you Anemoi. This is the case all over the
world, not just in Germany. Unfortunately there seems to be a culture of
shooting the messenger here, or accusing him of being “aggressive”,
“accusatory”, “claiming entitlement” or (my
On 14 December 2016 at 11:42, Andreas Krey wrote:
> On Wed, 14 Dec 2016 21:43:28 +, teor wrote:
> ...
> > The bwauth calculations do take latency into account, and they should:
> > if CPU usage or bandwidth are near their limit, the latency through the
> > relay will be high.
>
> I stand corr
On 14 Dec 2016 14:49, "Rana" wrote:
-Original Message-
From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf
Of Sebastian Niehaus
Sent: Wednesday, December 14, 2016 2:43 PM
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Tor relay from home - end of e
On 20 December 2016 at 19:23, Patrice wrote:
> Hi folks,
>
> my relay is running fine [zeiberschnitzel] and it got no errors. I can`t
> see anything in the logs either.
> But when I do the command
>
> #tor --verify-config
>
> I got these outputs:
>
> Dec 20 18:20:27.946 [notice] Tor v0.2.8.11 (gi
On 8 February 2017 at 09:37, Toralf Förster wrote:
>
> I do wonder about it b/c IMO this message is new - at least for me, or ?
The code seems to have been added 2 months ago, so this is probably
expected to appear after recent updates:
https://github.com/torproject/tor/commit/404e9e5611eff39
On 24 Feb 2017 10:14, "Volker Mink" wrote:
Hey there J
I just want to name a good provider for TOR Relays and Exits.
I am running a small VPS on Scaleway.com , which costs me about 3€ a month.
Unlimited traffic!
Scaleway is running ARM-systems, so ArchLinux is recommended.
The have x86 one
On 28 February 2017 at 17:32, Arisbe wrote:
> Hello all,
> I run a variety of Tor relays--most on VPS hosts. I recently added a small
> relay and updated my family members. Strangely, this last relay is tagged
> as an "alleged family member," even on itself [0]. It has been like this for
> over
Last night for 4h30 (until VPS provider shut it down) one of my middle
relays seems to have got in a bad state where it was using 100% CPU
continuously
It was not using much bandwidth, about 4MB/s, but reading the logs it
seems it was getting a lot of circuit requests (70K/minute initially,
100K a
On 28 Jul 2017 6:59 am, "Roger Dingledine" wrote:
On Thu, Jul 27, 2017 at 08:48:35PM +0300, Vort wrote:
> > This sort of thing has been going on for many years. I used to
refer
> > to it as "mobbing". As nearly as I was ever able to determine, the
behavior
> > is an unintended consequence
On 22 September 2017 at 16:49, Iain R. Learmonth wrote:
> Hi teor,
>
> On Fri, Sep 22, 2017 at 11:14:07PM +1000, teor wrote:
>>
>> > On 22 Sep 2017, at 23:03, relay 000 wrote:
>> >
>> >> Someone is using the hidden service rendezvous protocol to ask non-exit
>> >> relays to scan non-tor IP addres
I got also 17 from ovh (under ip-54-36-51.eu) and plenty of
leaseweb.com (didn't count) too but no your-server.de
The OVH ones were interestingly 2 (nearby) consecutive blocks of 4 and
13 IPs (and are not relays)
On 22 December 2017 at 15:23, Tyler Johnson wrote:
> Every IP I was checking thro
uktra tor[23419]:
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fbb01af9bfb]
Jun 05 03:17:59 mkuktra tor[23419]:
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fbb01afffc6]
Any idea ??
Pascal
smime.p7s
Description: Signature cryptographique S/MIME
___
On 3 July 2018 at 14:53, nusenu wrote:
> Dear debian/ubuntu tor alpha repo users,
>
> there is an oddly high number of
> relays running 0.3.3.5-rc
> which was the last version before the 0.3.3.x alpha repo
> has been discontinued.
>
> If you are doing apt upgrades and don't get tor v0.3.3.7 your s
On 7 July 2018 at 19:42, nusenu wrote:
>>> bonus points if you want to share
>>> the reason why you had a misconfigured sources.list
>>> file (maybe we can improve / avoid that somewhere)
>>
>> I had the problem on one of my relays because I was running "apt-get
>> update && apt-get upgrade" which
On 7 July 2018 at 19:54, nusenu wrote:
> bonus points if you want to share
> the reason why you had a misconfigured sources.list
> file (maybe we can improve / avoid that somewhere)
I had the problem on one of my relays because I was running "apt-get
update && apt-get up
On 7 July 2018 at 20:02, nusenu wrote:
>
>>> maybe it would be a good idea to switch to unattended-upgrades?
>>
>> I have never managed to get it to work :(
>> I have set it up on several machines and nothing ever got upgraded
>> whatever the config I set.
>> After spending too much time trying t
I got my IP address reported as changed to some Deutsche Telekom IP
twice in a few minutes by 154.35.175.225 yesterday
This IP is "Faravahar" according to
https://trac.torproject.org/projects/tor/ticket/14487
Jun 09 12:21:50.000 [notice] Our IP Address has changed from
149.18.2.82 to 91.5.121.93;
On 24 June 2015 at 03:09, Steve Snyder wrote:
> On Tuesday, June 23, 2015 9:07pm, saitos...@ymail.com said:
>
>> Besides the obvious requirements of a good relay (e.g. speed, geo-diversity,
>> constant uptime), what qualities make a relay valuable to the Tor network
>> and its
>> users?
>
> A qua
On 2 July 2015 at 10:45, Joshua Lee Tucker wrote
> Hash: SHA256
>
> Hi Karsten,
>
> I've made a patch to the page to add the HTML5 date components - it should
> work nicely across the majority of browsers (maybe even all with a plaintext
> fallback).
>
> I wasn't sure exactly in which format you w
On 20 July 2015 at 15:12, Karsten Loesing wrote:
>
> On 20/07/15 11:40, Pascal Terjan wrote:
>> On 2 July 2015 at 10:45, Joshua Lee Tucker
>> wrote
>>> Hash: SHA256
>>>
>>> Hi Karsten,
>>>
>>> I've made a patch to the page to
On 22 July 2015 at 10:44, Rejo Zenger wrote:
> ++ 21/07/15 20:59 +0200 - Jan Hendrik den Besten:
>>I have my node running here in The Netherlands at UPC, now merged with
>>Ziggo. I contacted them once: back then they did not have a problem running
>>even an exit node.
>
> If that is a connection a
On 23 July 2015 at 13:22, Toralf Förster wrote:
> -BEGIN PGP MESSAGE-
> Charset: utf-8
> Version: GnuPG v2
>
> hQQOA9vCYl42+L0WEBAArg1D4faK3HdxN9Zqql89LPgFAdUVfIuyS+HdMpeHYGcU
[...]
> -END PGP MESSAGE-
You message seems encrypted with your own key so only you can read it.
gpg: en
On 26 July 2015 at 17:48, Yawning Angel wrote:
> On Sun, 26 Jul 2015 16:11:56 +0200
> nusenu wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> [split from 'Giving away some "pre-warmed" relay keys for adoption']
>
> Ok.
>
>> > I'm of the opinion that it may be worth adding code
On 26 July 2015 at 22:42, Yawning Angel wrote:
> On Sun, 26 Jul 2015 22:32:18 +0100
> Pascal Terjan wrote:
> [snip]
>> > I question the usefulness of most of the relays running on
>> > residential lines in the first place for other reasons (Eg: most
>> >
On 17 August 2015 at 21:23, Tor Tor wrote:
> Hi,
> I'm running a relay node [1], and it's been up for a few days over 68 days.
> I was thinking it would get the guard flag around then. It has yet to get
> the flag or have non-zero guard probability. Any idea why that is? Or what I
> could do to ge
On 9 September 2015 at 01:28, I wrote:
> " we will have to suspend service. You will be immediately contacted about
> any issue that arises."
>
> Doesn't their statement say they will only suspend the exit to talk to you
> about what to do?
I think that matches "not too friendly", it would be m
On 22 October 2015 at 19:22, Logforme wrote:
> I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34)
>
> Saw this in yesterday's log file:
> Oct 22 03:17:55.000 [notice] Our IP Address has changed from
> 84.219.173.60 to 154.35.32.5; rebuilding descriptor (source:
> 154.35.175.225).
Nov 04 17:06:00.000 [notice] Our IP Address has changed from
149.18.2.82 to 154.35.32.5; rebuilding descriptor (source:
154.35.175.225).
Nov 04 17:08:55.000 [notice] Our IP Address has changed from
154.35.32.5 to 149.18.2.82; rebuilding descriptor (source:
154.35.175.225).
5.32.35.154.in-addr.arpa
On 17 December 2015 at 14:07, Nick Mathewson wrote:
>
> For the initial fallback release, we will only add your relay if you
> opt in. Please reply on the tor-relays mailing list, if you are able.
> (Opt-ins, opt-outs, and fallbacks chosen for inclusion in tor, will be
> managed using lists in the
I haven't been able to access BA website from home for the last few weeks.
I have failed to get any other answer on the phone that to try using
Internet Explorer or to wait for things to maybe get fixed. Twitter
support was not more helpful.
I am now wondering is this is because I run a (non exit
Yes
On 20 May 2016 at 12:21, Josef 'veloc1ty' Stautner wrote:
> Hi,
>
> do you host your mentioned relay on the IP which you use to access the
> website?
>
> ~Josef
>
> Am 20.05.2016 um 13:18 schrieb Pascal Terjan:
>> I haven't been able to acces
des. They don't differ between Exit- and Non-Exit Relays.
>
> ~Josef
>
> Am 20.05.2016 um 13:25 schrieb Pascal Terjan:
>> Yes
>>
>> On 20 May 2016 at 12:21, Josef 'veloc1ty' Stautner wrote:
>>> Hi,
>>>
>>> do you host you
On 20 May 2016 at 12:35, Roman Mamedov wrote:
> On Fri, 20 May 2016 12:18:01 +0100
> Pascal Terjan wrote:
>
>> I am now wondering is this is because I run a (non exit) relay. Can
>> anyone confirm if they also have the problem?
>> http://ba.com/
>>
>>
&
On Tuesday, June 21, 2016 09:52:43 AM Tristan wrote:
> But the point of Tor is to promote open access to the Internet. Once Tor
> starts filtering traffic, it's no better than the government censorship so
> many people use Tor to get around. They'd go from one filter to another.
This is not such a
On 26 June 2016 at 18:39, Yuriy M. Kaminskiy wrote:
> On 26.06.2016 16:22, pa011 wrote:
>>
>> On start-up my Exit (Linux 3.16.0-4-amd64) Tor 0.2.7.6 creates this log
>> message:
>>
>> [warn] OpenSSL version from headers does not match the version we're
>> running with. If you get weird crashes, t
On Thu, 3 Aug 2023, 15:57 Roman Mamedov, wrote:
> On Tue, 1 Aug 2023 23:14:28 +0200
> Eldalië via tor-relays wrote:
>
> > Hello there!
> > I've been running for over 1.5 year a middle relay on an IP address I
> also use
> > to browse, withous issues. However it's now some weeks since many
> webs
On 24 July 2018 at 17:38, Richard Johnston wrote:
>
> I've run a relay for over a year and recently updated from an RPI2 to a
> RPI3. I've copied the torrc file and the node has the same IP Address and
> ports. What additional files need to be copied to get the fingerprint (et
> al) to match the o
On 6 August 2018 at 11:00, teor wrote:
> Hi,
>
> Due to a recent CollecTor outage, we are missing consensuses from
> 2018-08-04 19:00 to 2018-08-05 17:00 UTC. We can recover about 16 of
> the missing consensuses, but we are still looking for the older 7.
>
> If your relay is:
> * running 0.3.1.1-a
On Thu, 30 Aug 2018, 14:11 Nathaniel Suchy, wrote:
> So this exit node is censored by Turkey. That means any site blocked in
> Turkey is blocked on the exit. What about an exit node in China or Syria or
> Iraq? They censor, should exits there be allowed? I don't think they
> should. Make them rel
Nathaniel Suchy, wrote:
> That’s a website blocking Tor users. Not a Tor Exit blocking a website.
> On Thu, Aug 30, 2018 at 7:06 PM Pascal Terjan wrote:
>
>>
>>
>> On Thu, 30 Aug 2018, 14:11 Nathaniel Suchy, wrote:
>>
>>> So this exit node is censore
he Tor Network. Will we sit idly by and allow it?
>
> On Thu, Aug 30, 2018 at 7:17 PM Pascal Terjan wrote:
>
>> A country's ISPs blocking some websites is not the exit blocking it and
>> the result is the same than websites blocking the country, users of that
>>
On Wed, 27 Mar 2019 at 22:10, I wrote:
>
> Where is the equivalent of https://www.torproject.org/docs/debian.html.en?
https://2019.www.torproject.org/docs/debian.html.en (From the
Documentation link at the top)
___
tor-relays mailing list
tor-relays@li
On Sun, 5 Jul 2020 at 17:36, nusenu wrote:
>
> Hi,
>
> I'm currently writing a follow-up blog post to [1] about a large scale
> malicious tor exit relay operator
> that did run more than 23% of the Tor network's exit capacity (May 2020)
> before (some) of it got reported to the bad-relays team a
On Tue, 7 Jul 2020 at 10:20, Karsten Loesing wrote:
>
> On 2020-02-12 16:05, Karsten Loesing wrote:
> > Hi relay operators,
> >
> > as you might have heard, MaxMind has changed access and use of their
> > GeoLite2 databases:
> >
> > https://blog.maxmind.com/2019/12/18/significant-changes-to-access
On Mon, 10 Aug 2020 at 14:56, tor-operator-sahara-it
wrote:
>
> Hello.
>
> On Tails:
> Today i found that my jabber messenger (with server in *.onion) use onion
> circuit with three nodes, and two times from two exit-nodes were very strange.
I believe the point of using a .onion service is that
On Wed, 2 Feb 2022 at 11:05, UDN Tor via tor-relays <
tor-relays@lists.torproject.org> wrote:
>
> > Note we believe some of these IPs are part of the Meris or Dvinis
> > botnets. If you are a residential Internet service provider, it is
> > possible that your customers' routers themselves have be
64 matches
Mail list logo
