[tor-relays] Shutdown relay 366BC592BC0154C0CD1D35C0E77D8F2C7F0B843E, upcoming shutdown 328E54981C6DDD7D89B89E418724A4A7881E3192

2018-03-05 Thread Stijn Jonker
Dear all, This is to announce that with immediate effect I have shutdown relay sjc02/366BC592BC0154C0CD1D35C0E77D8F2C7F0B843E and will do so in about a year and half with sjc01/328E54981C6DDD7D89B89E418724A4A7881E3192 as it's a fallback directory. Thanks for all the support on the mailing

Re: [tor-relays] Exit Relay

2018-03-05 Thread teor
On 6 Mar 2018, at 12:27, Damian Johnson wrote: >> A circuit getinfo sounds like a great feature. I'd be happy to review >> a proposal, but I'm not sure I'd have time to implement it. > > No worries! As mentioned, we already have a proposal. Eight years ago > Nick

Re: [tor-relays] Exit Relay

2018-03-05 Thread Damian Johnson
> A circuit getinfo sounds like a great feature. I'd be happy to review > a proposal, but I'm not sure I'd have time to implement it. No worries! As mentioned, we already have a proposal. Eight years ago Nick encouraged me to write proposals for things I'd find helpful, but of course a proposal

Re: [tor-relays] Exit Relay

2018-03-05 Thread teor
On 6 Mar 2018, at 11:29, Damian Johnson wrote: >> Does Tor export a list of connections over the control port? > > Hi teor. Nope, tor doesn't. That's something I wanted many years ago > and I made a proposal, but Jake talked me into limiting it to circuits > instead... >

Re: [tor-relays] Exit Relay

2018-03-05 Thread Damian Johnson
> Does Tor export a list of connections over the control port? Hi teor. Nope, tor doesn't. That's something I wanted many years ago and I made a proposal, but Jake talked me into limiting it to circuits instead...

Re: [tor-relays] Exit Relay

2018-03-05 Thread teor
> On 6 Mar 2018, at 11:06, Damian Johnson wrote: > > For what it's worth here's where Nyx decides to label a connection as > being an exit. The conditional is "if I can't resolve this to a relay > and our exit policy allows exiting to it then label as an exit"... > >

Re: [tor-relays] Exit Relay

2018-03-05 Thread Damian Johnson
Hi Roger, I don't think thats' the issue here. The lines they cited were exit connections, not the 'Exit' circuit lines (the later look different and don't include scrubbing). For what it's worth here's where Nyx decides to label a connection as being an exit. The conditional is "if I can't

Re: [tor-relays] Exit Relay

2018-03-05 Thread Roger Dingledine
On Mon, Mar 05, 2018 at 10:02:10AM +, Gary wrote: > What is going on here? I am confused as to why there is exit connections > but I am not / dont want an exit relay. I am guessing those are self-reachability tests and self-speed tests that your relay does by making circuits back to itself.

Re: [tor-relays] CPU saturation attack/abuse

2018-03-05 Thread torix
Dear Dhalgren Tor, I have been running a middle node with the ingress connexions being 5-10% fewer than egress connexions since it started about 11 months ago. changing Tor versions twice has not made any difference in this, the current version being 0.3.2.10 that came out yesterday. But I'm

Re: [tor-relays] Publishing bridge contact information

2018-03-05 Thread nusenu
Roger Dingledine: > And speaking of > community-building, are there volunteers lined up who would contact > bridge operators if given the chance, or is this more of a theoretical > "maybe it would happen"? I'll eventually add a check for "is exit operator also a bridge operator?" and might

Re: [tor-relays] Exit Relay

2018-03-05 Thread Gary
Hello, On Mon, Mar 5, 2018 at 2:49 AM, teor wrote: > I think this is a bug in arm. > Try nyx. I switched to nyx and it is fine allthough on deeper inspection the IP to is actually my IP so clearly this is a bug. On 5 March 2018 at 18:18, Damian Johnson

Re: [tor-relays] Exit Relay

2018-03-05 Thread Damian Johnson
Oops! Actually, this would happen with Nyx too. This is a Stem bug... https://trac.torproject.org/projects/tor/ticket/25423 Thanks for the catch! On Mon, Mar 5, 2018 at 2:49 AM, teor wrote: > > >> On 5 Mar 2018, at 21:02, Gary wrote: >> >>

Re: [tor-relays] New releases today: please consider upgrading.

2018-03-05 Thread Logforme
There are new security releases today. The official announcement just went to tor-announce, but I want to make sure that people on this list see it too. The debian package showed up today. I upgraded from 3.2.9 to 3.2.10 and removed my firewall connection limits. My early first impressions

Re: [tor-relays] Exit Relay

2018-03-05 Thread teor
> On 5 Mar 2018, at 21:02, Gary wrote: > > Hello. > > I have configured my relay (jaffacakemonster2) to be non exit, however arm > shows me the following (I edited out IPs' & some lines after copy/paste from > connection screen for others security / brevity) >

[tor-relays] Exit Relay

2018-03-05 Thread Gary
Hello. I have configured my relay (jaffacakemonster2) to be non exit, however arm shows me the following (I edited out IPs' & some lines after copy/paste from connection screen for others security / brevity) Connections (1878 inbound, 2113 outbound, 19 exit, 1 control) IP--> :443 (HTTPS)

Re: [tor-relays] Firewalls

2018-03-05 Thread TorGate
a network. regards Steffen TorGate torgate(at)linux-hus.dk OpenGPG 7FD5 65EF A4EF EEF3 7A13 4372 8409 49D6 01A2 0890 > Am 05.03.2018 um 07:18 schrieb Quintin : > > On Fri, Mar 2, 2018 at 10:04 AM TorGate >