Re: [tor-relays] Digital Ocean - running Exit node locked

I'm running on DO as well with the reduced exit policy and have had about five complaints in 2 months. DO certainly appears to be getting less and less happy. I'm glad to know it's not just me, though. Hopefully a curated list of IPs to reject will help a lot. Thanks for the link to tornull.

Re: [tor-relays] Digital Ocean - running Exit node locked

On 08.10.16 00:00, Markus Koch wrote: > reduced-reduced exit policy. ? The reduced-reduced policy variant is shown here: https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy -Ralph ___ tor-relays mailing list

Re: [tor-relays] Digital Ocean - running Exit node locked

reduced-reduced exit policy. ? Illuminate me, pls. Markus ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Digital Ocean - running Exit node locked

# The following sets which ports can exit the tor network through you. For more # information and updates on the suggested policy see: # https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy ExitPolicy accept *:53# DNS # ports for general internet browsing ExitPolicy reject

Re: [tor-relays] Digital Ocean - running Exit node locked

Thanks Markus - you are obviously well experienced with them :-) We should meet some day and share this and others.. Paul Am 07.10.2016 um 23:33 schrieb Markus Koch: > They will kick you after 2-3 months. Delete account, make new account. > They will kick you after 2-3 months. Delete account,

Re: [tor-relays] Digital Ocean - running Exit node locked

They will kick you after 2-3 months. Delete account, make new account. They will kick you after 2-3 months. Delete account, make new account. They will kick you after 2-3 months. Delete account, make new account. They will kick you after 2-3 months. Delete account, make new account. Welcome to

[tor-relays] Digital Ocean - running Exit node locked

Seems like even DO is not very much in favour of running Exits any more ? Anybody made the same experience - how to handle this please ? Thanks and Regards Paul "Hello -Although we do not specifically disallow TOR exit nodes, as the account holder you are responsible for all the traffic

Re: [tor-relays] Politically correct?

Tor is not perfect and everyone would be wise to learn as much as possible about its limitations (I'd start here: https://www.torproject.org/download/download.html.en#warning). It's still a very useful privacy tool though. Snowden: "I think Tor is the most important privacy-enhancing technology

Re: [tor-relays] Middle Relay changed to Exit Relay Bandwidth Change

It's very normal for exit relays to pick up *much *more traffic than middle or guard. Because exit relays have to deal with the abuse complaints of Tor users, there are much fewer exit relays than middle and guard: http://rougmnvswfsmd4dq.onion/relayflags.html Even though there is plenty of

[tor-relays] Politically correct?

Hello list members, for simple - political - reasons, i began contributing otherwise wasted bandwith to the tor network about half a year ago. And i am reading this list. Lately, there has been a discussion (Intrusion Prevention System Software - Snort or Suricata), that brought up some opinions

[tor-relays] Middle Relay changed to Exit Relay Bandwidth Change

Recently I enable exits on my relay and traffic seemed to jump very high compared to the almost stagnant bandwidth increase wen it was just running as a guard middle relay. I was wondering if this was normal for the traffic to jump this much. Here's the Atlas link for my relay:

Re: [tor-relays] Relay uptime after restarting Tor service

Nothing you do actually gets you a tshirt. The knowledge that you qualified for a tshirt is your only badge of honour. > -Original Message- ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] new warn message: Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS.

pa011: > Several of those warnings here as well on Oct 06 - on exit as on non > exit - at different times Sure, type of relay doesn't matter here since a rendezvous client picks random relay to act as Rendezvous Point. Somehow there are clients who send more than one ESTABLISH_RENDEZVOUS cell to

Re: [tor-relays] new warn message: Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS.

Am 07.10.2016 um 20:20 schrieb Green Dream: > One of my guard relays has a few entries on Oct 06 also: > > Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in > ESTABLISH_RENDEZVOUS. > Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in > ESTABLISH_RENDEZVOUS. > Oct 06

Re: [tor-relays] new warn message: Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS.

One of my guard relays has a few entries on Oct 06 also: Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS. Oct 06 09:04:00.000 [warn] Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS. Oct 06 10:17:30.000 [warn] Duplicate rendezvous cookie in

Re: [tor-relays] new warn message: Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS.

Toralf Förster: > nope, from "git blame" the appropriate line is part of git commit > 339df5df and that commit is already part of tor-0.2.4.11-alpha : > > commit 339df5df085e2115c01881cf628abe5ed3fbd456 I'm unable find change to this line in 339df5df085e2115c01881cf628abe5ed3fbd456. AFAICT,

Re: [tor-relays] new warn message: Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/06/2016 06:29 PM, Logforme wrote: > Maybe they are new in 0.2.8.8? nope, from "git blame" the appropriate line is part of git commit 339df5df and that commit is already part of tor-0.2.4.11-alpha : commit

Re: [tor-relays] Relay uptime after restarting Tor service

On 10/07/2016 12:55 PM, Zac wrote: > that my uptime on Atlas is reset to zero when I need to restart > the service, i.e. for updates or configuration changes. > Is this expected behaviour Yes signature.asc Description: OpenPGP digital signature ___

Re: [tor-relays] Relay uptime after restarting Tor service

That's normal. You should reload rather than restart tor for config changes though. And in case you're wondering, it doesn't affect your t shirt eligibility :-) albino On 7 October 2016 11:55:19 BST, Zac wrote: >Hi, > >I run this relay:

[tor-relays] Relay uptime after restarting Tor service

Hi, I run this relay: https://atlas.torproject.org/#details/02928855BFAD787F8B363F21860D1E7D156E0655 and noticed that my uptime on Atlas is reset to zero when I need to restart the service, i.e. for updates or configuration changes. Is this expected behaviour, or should the uptime in fact be

Re: [tor-relays] numtcpsock prevents relay from working properly.

Hi Moritz, thanks for your reply. This is very helpful. I think I will raise the issue with my provider and see how it goes. Best, Erik Moritz Bartl: > Hi Nils, > > Yes, this is a known problem. It has been discussed a number of times > before on this list, but it never made it into any FAQ. >

Re: [tor-relays] numtcpsock prevents relay from working properly.

Hi Nils, Yes, this is a known problem. It has been discussed a number of times before on this list, but it never made it into any FAQ. On 10/07/2016 11:38 AM, Nils Erik Flick wrote: > Asking customer service would mean explicitly drawing attention to the > fact that I'm trying to use the cheap

[tor-relays] tor relay and syslog logging

I'm trying to log locally (notice.log) and to a local syslog-ng server. It doesn't seem to work. I get no messages at all to my local syslog server. When I try to log some testlines manually (even as the tor system user) it seems to work. As I understood the configuration I can have multiple

Re: [tor-relays] new warn message: Duplicate rendezvous cookie in ESTABLISH_RENDEZVOUS.

x2 too on a non-exit relay : Oct 06 13:35:22.000 (UTC+2) But nothing a 2nd relay process on the same machine... 06/10/2016 18:29, Logforme : > I had 3 today on my non-exit relay. Can't remember seeing them before. Maybe > they are new in 0.2.8.8? > Times are UTC+2 > > Oct 06 09:14:03.000