[tor-relays] Failing: 4063 Connection error

[Kurt Besig]

Where can I set the connection limit higher or is this a result of max
bandwidth allowed?
This relay was up for over a year with no issues, however since updating
the Tor version it's been problematic at best.
Thanks.
Linux version 2.6.32-042stab125.5 (r...@kbuild-rh6-x64.eng.sw.ru) (gcc
version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Oct 17
12:48:22 MSK 2017

Tor version 0.3.1.9

:Failing because we have 4063 connections already. Please read
doc/TUNING for guidance. [over 1601 similar message(s) suppressed in
last 21600 seconds]




signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] No Gaurd

[Kurt Besig]

https://atlas.torproject.org/#details/E65D300F11E1DB12C534B0146BDAB6972F1A8A48

Relay looks pretty stable to me, I'm re-visiting the lack of guard
status... ideas?



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Horizons Relay Figerprint

[Kurt Besig]

E65D300F11E1DB12C534B0146BDAB6972F1A8A48



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] A Common Thread: Guard Status

[Kurt Besig]

Just curious and I know it's probably been answered 100x times... I
recently updated Tor to an, 'approved version', after 340+ days of up
time. Upon restarting the relay, 25 days ago, Ive not been given the
'guard flag' again. Why?

Thanks



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Tor Install Error

[Kurt Besig]

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 following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
74A941BA219EC810

W: Failed to fetch
http://deb.torproject.org/torproject.org/dists/trusty/InRelease

I've read several approaches to remedying this error, however I'm
wondering what would be the 'most widely accepted as correct' method of
dealing with the error?

Thanks



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors

[Kurt Besig]

On 1/5/2017 6:50 PM, Roger Dingledine wrote:
> On Thu, Jan 05, 2017 at 06:38:23PM -0800, Kurt Besig wrote:
>> I just installed tor on a Raspberry Pi 3 Model B and can't get a relay
>> to start unless I sudo. When I attempt to start tor as a non-privileged
>> user I get a permissions error: Opening Jan 05 18:33:35.929 [notice]
>> Opening OR listener on 0.0.0.0:443
>> Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:443: Permission denied
>> Jan 05 18:33:35.930 [notice] Opening Directory listener on 0.0.0.0:80
>> Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:80: Permission denied
>>  Ideas on best method to bind these ports to tor on startup as non-root?
> 
> If you're using the deb, it's actually intended to be started as root
> ("service tor start"), and it drops privileges once it binds to the ports.
> 
> Using the deb init script is also smart because it does things like fixing
> "ulimit -n" for you so it doesn't default to 1024 (which is way too low
> for a useful relay).
> 
> If you want to use iptables rules to do forwarding instead, check out
> https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls
> 
> (We haven't moved that faq entry to the main faq because the deb just
> handles it for you.)
> 
> (All of this might be a lie for Raspbian. I hope not though.)
> 
> --Roger
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
What a great community, all terrific suggestions to my problem. I tried
easy first, Roger's suggestion, and voila! A check of /var/log/tor/log
indicates all is well. Sometimes simple is best. Now let's see if the
relay's descriptor gets published and what bw adjustments are necessary.
One of our more vocal ops and all her questioning got me interested in
trying out an inexpensive alternative, so we'll see what opinions,
questions, suggestions, I come up with. :-)

Thanks again.




signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors

[Kurt Besig]

I just installed tor on a Raspberry Pi 3 Model B and can't get a relay
to start unless I sudo. When I attempt to start tor as a non-privileged
user I get a permissions error: Opening Jan 05 18:33:35.929 [notice]
Opening OR listener on 0.0.0.0:443
Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:443: Permission denied
Jan 05 18:33:35.930 [notice] Opening Directory listener on 0.0.0.0:80
Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:80: Permission denied
 Ideas on best method to bind these ports to tor on startup as non-root?

Thanks

sorry for the dup..



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Raspberry Pi + Raspbian GNU/Linux 8.0 (jessie) + bind errors

[Kurt Besig]

I just installed tor on a Raspberry Pi 3 Model B and can't get a relay
to start unless I sudo. When I attempt to start tor as a non-privileged
user I get a permissions error: Opening Jan 05 18:33:35.929 [notice]
Opening OR listener on 0.0.0.0:443
Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:443: Permission denied
Jan 05 18:33:35.930 [notice] Opening Directory listener on 0.0.0.0:80
Jan 05 18:33:35.930 [warn] Could not bind to 0.0.0.0:80: Permission denied
 Ideas on best method to bind these ports to tor on startup as non-root?

Thanks



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Faravahar acting up again / "Bad Gateway" while uploading descriptor

[Kurt Besig]

On 1/5/2017 1:29 PM, anondroid wrote:
> I just set up a handful of new relays, and all of them have something
> like the following in their logs:
> 
>   [WARN] http status 502 ("Bad Gateway") reason unexpected while
> uploading descriptor to server '154.35.175.225:80'
>   [WARN] Received http status code 502 ("Bad Gateway") from server
> '154.35.175.225:80' while fetching...
> 
> This appears to be related to the authority Faravahar. I know this has
> happened before but I wanted to make sure the proper people were aware
> of the issue.
> 
> Thanks.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
I just stated up a new relay as well and received the same error. This
is the first time after running relays for several years that I've seen
this error/status code. A side note: this is also the first relay I've
run from the same LAN with the same ip, all others are on different VPS'.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Inconsistent BW measurements of unused relay

[Kurt Besig]

On 12/11/2016 1:43 PM, Rana wrote:
>> On 12 Dec. 2016, at 01:56, Rana  wrote:
>>
>> OK Tim thanks for the answers, I appreciate your patience with me 
>> [even though I "lack programming skills" :) ]
>>
>> The one answer of yours that still does not make sense to me is that 
>> arm actually means Kbytes/sec and not kbits/sec  when it writes Kb/s
>>
>> I have arm reporting average  of at least several tens of Kb/s all the time, 
>> and about 100 Kb/s most of the time,  and then I wind up with almost 
>> constant 200 bit/sec actual average rate over 6 hours, based on the total 
>> number of Mbytes sent that Tor reports in its log file. 
>>
>> Even if the 200 bit/sec figure is somehow rounded to 8000 bit/ sec or 
>> even 8000 bytes/sec as you suggested , this does not make sense…
> 
> Ok, so you didn't say that to start with, you seemed to be saying that it was 
> constantly showing 100 kb/s.
> 
> Perhaps arm is displaying your maximum bandwidth over a certain time?
> (I really don't now what bandwidth arm measures.)
> 
> T
> 
> I do not have a slightest freaking idea and this arm thing seems to have been 
> written by anarchists who thought that documentation was too bourgeois
> 
> Rana
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
When I first began running  Tor relays I felt a dependency regarding arm
and it's output as well. However, over the years I weened myself off arm
and just let the relay run without constant worries. I believe this is
the feeling of most operators. When I feel the need I run nload and
Vnstat is handy for analysis. Command line lsof and many others do a
good job as well.
Again, just offering my 2 cents worthno attack intended..



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

[Kurt Besig]

On 12/4/2016 7:39 AM, Rana wrote:
>> For as little as $10.00 US there are VPS' with static ip's..
> 
> Attn: Kurt Besig
> 
> Well I kind o' like my Raspberry Pi that cost me $40 including box and power 
> supply and SD card and door to door delivery, with far more horsepower and 
> memory than needed for running Tor relay, and my free and absolutely stable 
> 1.5mbps that I want to donate to Tor courtesy of my ISP, and my transparent 
> Tor proxy and my hidden service  and my wireless access point that lurk on 
> the same Pi. 
> 
> This is not a good reason to punish my relay. Makes ZERO sense to me and to 
> who knows how many people like me whose relays are flushed down the drain by 
> the current DirAuth algorithms.
> 
> I can think of many an Iranian or Turkish or Chinese or Russian dissident who 
> could use 1.5 mbps bandwidth to communicate with the free world.
> 
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Late to the party however,I'm sorry if you interpreted my response as
being negative, actually I was offering one possible solution. Welcome
to the Community and thanks for running a Tor relay.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP

[Kurt Besig]

On 12/4/2016 1:03 AM, teor wrote:
> 
>> On 4 Dec. 2016, at 01:06, Rana  wrote:
>>
>> I have been running a relay with dynamic IP for a month now and quite 
>> obviously my relay is severely punished for having a dynamic IP. The IP may 
>> change once in several days (currently running over a week with the same IP 
>> and I just got my Stable flag back again, about 3 weeks after losing it). 
>> The relay’s throughput is a tiny fraction (less than 10%) of the actual 
>> capacity which I programmed the torrc file to donate. The capacity I wanted 
>> to donate is less than the uplink speed of my internet connection (the 
>> downlink speed is higher than downlink and is thus irrelevant here).
> 
> A slow ramp-up is normal, but you seem to be experiencing something
> different:
> 
> https://blog.torproject.org/blog/lifecycle-of-a-new-relay
> 
> Given what you said about the flags, it's likely the directory
> authorities' reachability and stability checks that are removing the
> flags from your relay:
> 
> https://gitweb.torproject.org/tor.git/tree/src/or/dirserv.c#n851
> https://gitweb.torproject.org/tor.git/tree/src/or/dirserv.c#n3170
> 
>> I started with a consensus rating of 21, which went up to 30 and then after 
>> a couple of IP changes collapsed to 13. It is now 14, and never went above 
>> this again,  with the relay running ALL THE TIME stably for a month minus a 
>> small number of restarts due to IP changes. As I said, stable IP for a week 
>> now and a Stable flag. 
> 
> The Tor bandwidth authorities don't store your relay's IP address, so
> it's probably not the bandwidth measurements that are the issue:
> 
> https://gitweb.torproject.org/pytorctl.git/tree/SQLSupport.py#n85
> 
>> 1.   Why is the relay with dynamic IP punished? This makes zero sense to 
>> me. IMHO changing an IP once a week and running stably between such changes 
>> is stable enough for all practical purposes. And since the fingerprint of 
>> the relay does not change when the IP is changed, dirauths know that this is 
>> the same stable node.
> 
> No, that's not strictly true, all the directory authorities know is that
> it is a node that has access to the same private key.
> 
> There are advantages to resetting when a relay's IP address changes:
> * a changed IP usually means a changed network with different
>   characteristics,
> * if the relay IP address changes, there's no guarantee it will be just
>   as reachable or stable at the new IP,
> * stolen keys become much less valuable,
> * duplicate keys / failover strategies are discouraged.
> 
> To resolve this issue, I recommend getting a static IPv4 address with
> your ISP, or renting a cheap VPS with a static IPv4 address.
> 
>> 2.   The “advertised bandwidth” that I see in Atlas has absolutely 
>> nothing to do either with the bandwidth that I advertise (it is 3-4 times 
>> larger than what I see in Atlas) or with the actual data throughput of my 
>> relay (it is 20 times smaller than what I see in Atlas). Can somebody 
>> explain this?
> 
> It's likely related to the fact that your relay is never on the same IP
> long enough to get the Stable or Fast flags, so no clients use it.
> 
> But I don't know your relay's fingerprint, so I can only repeat the
> general advice I have given others with similar questions:
> 
> https://lists.torproject.org/pipermail/tor-relays/2016-November/010913.html
> https://lists.torproject.org/pipermail/tor-relays/2016-November/010928.html
> https://lists.torproject.org/pipermail/tor-relays/2016-November/010916.html
> 
> (There are more if you search the list archives.)
> 
> That should be enough to get you started, if you'd still like specific
> advice after reading those threads, feel free to let us know your
> relay's fingerprint.
> 
> T
> 
For as little as $10.00 US there are VPS' with static ip's..



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Questions regarding arm on Debian

[Kurt Besig]

On 11/12/2016 8:34 AM, r1610091651 wrote:
> On Sat, 12 Nov 2016 at 12:41 Dennis Christ  > wrote:
> 
> Yes that is what i tried to do. But it does not work in my case.
> 
> $ arm
> [Errno 13] Permission denied: '/var/lib/tor/control_auth_cookie'
> 
> Even if my user is in the group debian-tor the user has no right to
> access /var/lib/tor.
> 
> $ ls -l /var/lib | grep tor
> drwx--S--- 4 debian-tordebian-tor4096 Nov 12 12:38 tor
> 
> 
> Am 12.11.2016 um 10:33 schrieb Louie Cardone-Noott:
> > On Fri, 11 Nov 2016, at 07:16 PM, diffusae wrote:
> >> Yes, you are right. But CookieAuthentication should work. You cannot
> >> query all of the connections without access to /var/lib/tor. You only
> >> will see circuits. I suggest to use "sudo -u debian-tor arm", if you
> >> like to use all of the arm pages. Otherwise you have to change the
> >> permissions. In my case, there is also the setgid flags on the
> >> directories (2700 drwx--S---).
> > Sorry not fully read the correspondence here but perhaps a tidier
> option
> > might be the one recommended on the tor website[1] of doing
> >
> > sudo adduser $USER debian-tor
> >
> > The alternative of running as the debian-tor user is a 'bad idea', see
> > [2] from last July
> >
> > [1] https://www.torproject.org/docs/tor-relay-debian.html.en#after
> > [2]
> >
> https://lists.torproject.org/pipermail/tor-relays/2016-July/009608.html
> 
>  
> Hi
> 
> You could just modify the systemd service file for tor, with something like
> ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d
> /var/run/tor
> ExecStartPre=/usr/bin/install -Z -m 02750 -o debian-tor -g debian-tor -d
> /var/log/tor
> 
> Cheers
> Seb
> 
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
A little OT, but if Arm is giving you trouble perhaps try using nload or
lsof to view activity on your relay. When I started running a tor relay
I was very dependent on Arm to, 'see what was going on', but over time I
realized that if things were going smoothly there was little need to run
a background app such as Arm.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] proper way to insert PGP key in torrc?

[Kurt Besig]

On 11/3/2016 11:15 PM, grarpamp wrote:
> On Thu, Nov 3, 2016 at 6:39 AM, Toralf Förster  wrote:
>> Not too much fun with such a lame relay I fear
> 
> He's running a relay because what he believe and it's fun
> without hurting nobody.. and you bash him not running
> with big dogs. Wtf bro.
> 
> Props to this guy and everybody that's running nodes
> on any crypto overlay network.
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
+1



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] ISP, Abuses , Intrusion Prevention etc.

[Kurt Besig]

On 10/11/2016 1:53 AM, Moritz Bartl wrote:
> On 10/11/2016 12:51 AM, Kenneth Freeman wrote:
> I set up my own ISP (AS28715) so I could run Tor exits etc without any
> trouble.
 Could you share a bit more about what is involved in doing that?
>>> I'd also be very interested in learning more about setting up an ISP
>>> for Tor. Is it a non-profit? How many man hours did it take (roughly)
>>> to get the structure in place? How much money (roughly) did it take?
>>> How much legal consultation did it require to setup?
>> I'm intrigued by this myself.
> 
> There are different phases or activities one might consider being part
> of "creating an ISP".
> 
> Legally, you "create an ISP" by operating a Tor exit relay.
> 
> As always, for exit relays, I strongly urge people to get listed in the
> WHOIS of the respective IP range, especially as abuse contact. As soon
> as you're listed there, a lot more people will regard you as "the ISP".
> 
> In theory it does not matter what type of legal entity is listed there;
> I know of hosting providers run by single individuals without another
> legal entity "around them", and it works just fine. Still, in many
> cases, if they see the name of an individual, they will more likely
> assume that you might be the culprit, than if it just lists an
> incorporated entity.
> 
> Then, the next step is to get your own Autonomous System Number. Quite a
> number of complaints don't go to the abuse contact listed in the IP
> range, but directly to the "upstream" Autonomous System operator. You
> "catch" these types of complaints by registering your own, and your own
> IP space. Then, the hunt for "exit friendly hosters" turns into a hunt
> for ISPs that will announce your IP space and your ASN.
> 
> In most jurisdictions, you do not register "common carrier-type"
> activities with the government; you have to register Internet _access_
> providers in certain jurisdictions (eg. Germany), but you do not _want_
> to be an _access_ provider with your exit relays.
> 
> To get an Autonomous System Number and IP space, the place to go to
> depends on _your_ jurisdiction: ARIN (US/CAN), RIPE (EU), APNIC (Asia),
> LANIC (Latin America), AFRINIC (Africa); IP ranges and ASNs can then be
> announced by any hosting provider.
> 
> For examples, see
> https://apps.db.ripe.net/search/query.html?searchtext=ZWIEBELFREUNDE
> 
Thanks for those insights, very useful and interesting.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Exit relay funding

[Kurt Besig]

On 8/3/2016 10:13 PM, Roger Dingledine wrote:
> On Wed, Aug 03, 2016 at 03:29:01PM +0200, t...@as250.net wrote:
>> Absolutely. Most of the infrastructure we provide on that basis and it
>> is ok! The reason for running that exit node was that we believed it
>> would contribute towards a positive impact in many peoples lives.
> 
> Thanks for contributing while you did!
> 
> I'm remembering way back when I would mail all the people running relays
> to see if they needed anything. Then there was the phase where we got
> some funding for Moritz to do relay operator advocacy and coordination:
> https://blog.torproject.org/blog/turning-funding-more-exit-relays
> and that push also led to some cool sites like
> https://compass.torproject.org/
> 
> Among all the things that we need to do next, I think getting a relay
> advocate / coordinator in place would sure be useful. I think there are
> so many things that we need, though, that it's going to be a while yet
> before we get such a person in place.
> 
> In the mean time, hang tight everybody, and let's continue to have a
> community who helps each other, and thanks all for your contributions.
> 
> --Roger
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Well stated and thank-you, Roger.
I agree 100% with the need for a more 'visible' advocacy in this age of
headline reading and jumping to false conclusions for no factual reason.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] biggest guard operator apparently left the tor network

[Kurt Besig]

On 2/28/2016 5:00 AM, nusenu wrote:
> Looks like SG.GS stopped their guard relays. They had >3% guard probability.
> 
> +---++--+
> | Con5  | lastseen   | fingerprint  |
> +---++--+
> | SG.GS | 2016-02-22 | 675C5A2C2EC403B6B583735191042CF489D4E5DA |
> | SG.GS | 2016-02-22 | C3D51AAF129FED507053244ADA29353D01AD5C90 |
> | SG.GS | 2016-02-22 | B9B927347E005256D5D48007C38208FE8F7CC3BE |
> | SG.GS | 2016-02-22 | 075A4D8D7662DF566FCE390FC820C539BFBBA867 |
> | SG.GS | 2016-02-22 | 53E2060F64DF258597E738FD5608D2939B92BC1D |
> | SG.GS | 2016-02-22 | 963ADC0137505151C1AFA6757DD2367EDEEC7B62 |
> | SG.GS | 2016-02-22 | B4697BA6520A17A7F51E613018754BA5FD46D0A0 |
> | SG.GS | 2016-02-22 | 951BDBA042A69FE8577129EA301B027A879B985B |
> | SG.GS | 2016-02-22 | D905EEADE0A40C7C0E6A8102708CF16AB8ED9A35 |
> | SG.GS | 2016-02-22 | 593B6169DA24F3835F0B485317C0DB529B8F3E58 |
> | SG.GS | 2016-02-22 | 0519D312F1BD9668B3B43751E0934911E4C79C79 |
> | SG.GS | 2016-02-22 | D9BFC55DDD8152F06D87C9DA7D192E86FC628626 |
> | SG.GS | 2016-02-22 | 38F423A4320380FFE32DB60B72E7457CD6E3F096 |
> +---++--+
> 
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
And what do you think this means to the network as a whole?



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] tor middle node question

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 1/26/2016 12:58 AM, Markus Koch wrote:
> hi,
> 
> as a good TOR support peon I got a dedicated server and set up TOR
> 3-4 weeks ago. Everything went great, I got my Guard, Fast and
> Stable etc. Flag and my little server was busy & happy. After
> restarting the TOR daemon I lost all my flags and even after 12
> hours I only got Running and Valid back. What went wrong?
> 
> My server is:
> https://torstatus.blutmagie.de/router_detail.php?FP=caf1eea0e8e8919dfc
480a885b8bd1da00d0ffb7
>
> 
> 
> Markus ___ tor-relays
> mailing list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Typical behavior after a restart, be patient and all will be well
again. :-)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWp2OOAAoJEJQqkaGlFNDPydgH/jE/8DlLL4l+jKUXe6rJAiAW
OOQYHSKDQeBDtwP3iDUBajKz2AUd9ipq499OHT+TgDUcSRbrOq7fGUHcjU8ZMh0L
4k0k0WdaMV5GQpqSirJUmYhXI8BqQ/2Mb+pd3d3Oqwd9PsIPgxmzqsUmKEYV+dCK
b3dLZXMLRtULCkVxtmuukk8RK2ZQKXXiRuvk98FVKxB6ARru323fjz3n7ue6HhKh
sXy1ZYQ19vEHAKAhO6wTmjiUAKl/T/xRsTMKrPt7TprfQapPm4zqWjBjchGrSRNc
WsPnb0RQina40LjPR3DZSdqQI5equQim02OrGmJKMaXYgvoKj5pAsopyLcz+cCo=
=4MS3
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

[Kurt Besig]

On 12/17/2015 6:07 AM, Nick Mathewson wrote:
> TL;DR: Stable non-exit relays can help tor clients use the Tor 
> network. Please opt-in!
> 
> We want to run a trial of fallback directory mirrors (fallbacks)
> in Tor. Tor clients contact fallbacks to download the consensus
> during initial bootstrap, before they contact the directory
> authorities.
> 
> Fallbacks allow Tor to bootstrap in networks that block the Tor 
> directory authorities. This allows people to use Tor without
> manually configuring bridges or pluggable transports.
> 
> For more information about fallbacks, see: 
> https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors
>
>  For this trial, we want to find around 100 stable non-exit relays,
> as exits currently experience high load.
> 
> We want relays that expect to be stable for the next 2 years,
> with:
> 
> good uptime, the same IP address(es) and port, the same relay
> identity key, good bandwidth and network connectivity.
> 
> In December 2015, we created a list of ~400 candidate fallbacks. 
> https://trac.torproject.org/projects/tor/attachment/ticket/15775/fallback_dirs.inc
>
>  If your relay is on this list, and you expect it to be on the same
> IP address(es) and port for at least 2 years, please consider
> opting-in for this trial. (Relays that aren't on the list are
> welcome to opt-in. They will be considered in future releases, or
> if the selection criteria change.)
> 
> 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 publicly available tor git
> repository.)
> 
> all best wishes, & thanks for running Tor! 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Relay was down during transition to new VPS, meets all criteria at
this point. Available if needed.
New Fingerprint: 'horizons E65D300F11E1DB12C534B0146BDAB6972F1A8A48'



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] VPS/Tor Final Thoughts

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I thought it might be helpful to any other volunteer that may have
been silently following this thread to quickly post the issues with my
VPS Tor server that were resolved.

1. Setting up iptables allowed connections to my server.

2. Adding my server's [ip address] to the /etc/torrc resolved the
problem of tor attempting to connect to the "node" my server is on
rather than the actual ip my server is on.

3. Checking the user groups and permissions necessary to allow access
to tor files.

Other thoughts: As mentioned numerous times arm is a comfy frontend,
but certainly not necessary after investigating system tools such as
lsof and utilizing nload or munin. Also having ntp installed and
running is helpful I think.

Again thanks for all the help and have a very happy holiday season!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWaDXxAAoJEJQqkaGlFNDPGh4H/0uDGiSIq9dYjDBNSIrVRoBQ
sBGjLdFhvdFSJ4dsTRPspAKC+6zg4FnGSj1isBFBmJOLIN71oIo6qXkrXoQgyS+Q
crnNYucyC6Vo8vQdK72QabuAJZGE2+VXfwTw/82NhldIQnKJzyfnjNKZYamR486y
KQJGzPHls2abZPu0zyx/ay7pZRUZWzGvfc1yShQ6yTsiVqCJk456aPRd0/rbkLMQ
dG/TOHHSOAJzMsZXk92rzk0JNBBYhwkOTiNyPQDd+S68IWyLXp5wC0hE4KTdRmf/
Osa8NIB3FQyYeg6XAjxZ1PhYSc8Lp91+K220znS/2lXStxjrdUFY4TU7119iYpA=
=a7HY
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] VPS/Tor

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I want to thank everyone for the multitude of great suggestions
regarding getting my relay up on a VPS. I reviewed every email and all
the input was useful.
The relay is up and running: E65D 300F 11E1 DB12 C534 B014 6BDA B697
2F1A 8A48
As well as my home relay: F527 3098 A711 F845 E5D1 A24F 9D38 F93B 86A0
F220
While all the information culminated in a successful outcome the
suggestion of installing ufw as a means of setting up iptables was
exceptionally valuable, thank you.
Hopefully in the future I can return the kindness.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWZZzuAAoJEJQqkaGlFNDPifYIAIGF6EZIxvuRCz2pTQa9+vg1
6OX1YJ/Z/fP4sGhhS+VtpGzhjewFf4Yv1FYXvWdRQWVW204Ms6wR6ibul4jLd58u
ENr75uDqK/ro8kLWQpWsLeJoh3zp8cAc5dpH/u9Itftj0o/td8fGVeV6YIOw9q3L
oA90pIVRNXun49Tb4cZjYm71+KBRwSekyXUoXccAcFzw+1WvLkW9TD8Xtd25/D7E
2VBfsYZinqia+7kqcCfUzoO4Ekg4JTkgBt/PkQ9eONz3w5g6+e52hh3kNurW3wfO
61BQ5Nq/0Q2u+cmgp+DItkD5+XSLPop8HZnwJM17M1nGxZ+/cBFYGZQmrlXpFUs=
=nGYI
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] VPS/Tor Almost There

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks again for all the support everyone has bee extremely helpful.
So, I reinstalled the OS on the VPS: lsb_release -d
Description: Ubuntu 14.04.3 LTS
uname -r  2.6.32-042stab102.9

Finally solved all the permissions problems, paths are correct, tor
and arm open properly.
The problem now boils down to this:
The VPS isn't allowing Ports 9001 and 9030
Should I investigate further getting my iptables up and running or
just contact the admin and have them allow the ports?
As I mentioned previously even after saving the tables upon reboot
iptables -L shows no rules, the file is empty.

 :~$ iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
 Any further suggestions would be appreciated.

Thanks
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWZF8qAAoJEJQqkaGlFNDPO18H/2Axj4EeGf5joYQ3n2SH1cgs
HhDAawaiMaSKMcfC/Oc9TudwKAxkoY+QkhegZr5senNKXrXjNPeLucfejkRBiUoJ
8KLOZabSGH2Uf89JNa4ZFbf9QVIiU8GdNJ0vSGy55iAuJQl14ZUpDRQeNnGkmwb5
uhADchwTVjK7Pq+ELyG6OI6l0jlQ69TWCpgH4lnMjQ5U+Nr1QKyApxXqr1ap5Heb
KJmlwchTv4zAxX2eBc1DPqAXdc9OsvEsPG/r/zp4Z/wPWxsUTGoZWoXsWv4xyjPQ
xzAzUKD+b+AvqGQ3ehQbdXtg423kO7/amVidAzux8mDmMeZuFoP3tpfqLd8cH+s=
=uoin
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 8:25 PM, Damian Johnson wrote:
> For what it's worth process permissions aren't at play here. Arm
> is failing to talk with the control port - permissions could cause
> us to be unable to read the authentication cookie, but that would
> be a different message.
> 
> Cheers! -Damian
> 
> 
> On Fri, Dec 4, 2015 at 5:36 PM, Manager Bahia del Sol LLC 
>  wrote:
>> 
>> No worries,
>> 
>> Are you sure the user or group is debian_tor? The default is
>> debian-tor in Ubuntu.
>> 
>> If that isn't the problem,
>> 
>> First I would be sure tor is actually running. top or top -u
>> debian-tor The second will show if tor is actually running as the
>> user you think it is.
>> 
>> If it is, then see if it is listening on the control port sudo
>> netstat -ntlp | grep LISTEN
>> 
>> If it is I would suspect that either a firewall is blocking that
>> port. If you have one running try shutting it down for a few
>> minutes while you try to start arm.
>> 
>> Or maybe it is a permissions issue where arm is not running as
>> the same user as tor. You could try starting arm as root to see
>> if it would start. But, do not run arm as root full time. Only
>> try to start it as a test.
>> 
>> 
>> 
>> -- Manager of Bahia del Sol LLC
>> 
>> 
>> ___ tor-relays
>> mailing list tor-relays@lists.torproject.org 
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> Dec 05 21:17:46.000 [notice] Your IP address seems to have changed
> to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46.000
> [notice] Our IP Address has changed from 142.4.217.95 to
> 167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE). 
> Dec 05 21:18:42.000 [notice] Your IP address seems to have changed
> to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com).
> Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
> from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
> METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05
> 21:18:43.000 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent. Publishing server
> descriptor. Dec 05 21:38:37.000 [warn] Your server
> (142.4.217.95:9030) has not managed to confirm that its DirPort is
> reachable. Please check your firewalls, ports, address, /etc/hosts
> file, etc. Dec 05 21:58:37.000 [warn] Your server
> (142.4.217.95:9030) has not managed to confirm that its DirPort is
> reachable. Please check your firewalls, ports, address, /etc/hosts
> file, etc.
I've gotten this far, not being much good at networking I can't tell
where the problem lies.. do I need to forward something?

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYzh6AAoJEJQqkaGlFNDPCeYIAJln5C5Z+7n69zcoW1/RdUxi
iduyKB/lnXc1Be190dSsHikjXVWv2hYvbnwvn3RuGOAft29WHd/OJi+GK9qBAB57
qdL+sl4PvlJVlWYH8hDK65FHqmZ85UYRX0nP5KsvRLbzKlNiX1rGSJPfpVSeOlK8
2bvSG/b4+Y4ZqmlxmLyJW5eJnMMzOHJdTf/OgUefnqic5KB1BLXygFi566lYYNMC
d8R8RObw8Rez/9H4+cKXcbNfnN2Yh0RMwpHF8nqpU8D292kO+Koz/xhfsu9VXRfe
DBKhCSfKdDJBNiP0zI13Y1OB5tq4SG0sKhhGCCavW+3oelT2ujyTBgB4xAyszkY=
=U+4y
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/5/2015 3:20 PM, Sean Greenslade wrote:
>>> Dec 05 21:17:46.000 [notice] Your IP address seems to have
>>> changed to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05
>>> 21:17:46.000 [notice] Our IP Address has changed from
>>> 142.4.217.95 to 167.114.35.28; rebuilding descriptor (source:
>>> METHOD=INTERFACE). Dec 05 21:18:42.000 [notice] Your IP address
>>> seems to have changed to 142.4.217.95 (METHOD=GETHOSTNAME
>>> HOSTNAME=ca3.pulseservers.com). Updating. Dec 05 21:18:42.000
>>> [notice] Our IP Address has changed from 167.114.35.28 to
>>> 142.4.217.95; rebuilding descriptor (source: METHOD=GETHOSTNAME
>>> HOSTNAME=ca3.pulseservers.com). Dec 05 21:18:43.000 [notice]
>>> Self-testing indicates your ORPort is reachable from the
>>> outside. Excellent. Publishing server descriptor. Dec 05
>>> 21:38:37.000 [warn] Your server (142.4.217.95:9030) has not
>>> managed to confirm that its DirPort is reachable. Please check
>>> your firewalls, ports, address, /etc/hosts file, etc. Dec 05
>>> 21:58:37.000 [warn] Your server (142.4.217.95:9030) has not
>>> managed to confirm that its DirPort is reachable. Please check
>>> your firewalls, ports, address, /etc/hosts file, etc.
>> I've gotten this far, not being much good at networking I can't
>> tell where the problem lies.. do I need to forward something?
> Check your firewall, and gateway port forwards if the server is
> behind a NAT. If you're not sure where to start, post the output of
> "sudo iptables -L"
> 
> --Sean ___ tor-relays
> mailing list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
I've made several iptables and saved them, I thought, however every
time I reboot the VPS all my rules are gone.
~$ sudo iptables -L
> Chain INPUT (policy ACCEPT) target prot opt source
> destination
> 
> Chain FORWARD (policy ACCEPT) target prot opt source
> destination
> 
> Chain OUTPUT (policy ACCEPT) target prot opt source
> destination


but:
 cat /etc/iptables.rules
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*raw
:PREROUTING ACCEPT [2424:210831]
:OUTPUT ACCEPT [1856:540218]
COMMIT
# Completed on Fri Dec  4 04:30:56 2015
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*nat
:PREROUTING ACCEPT [229:8057]
:POSTROUTING ACCEPT [86:5885]
:OUTPUT ACCEPT [86:5885]
COMMIT
# Completed on Fri Dec  4 04:30:56 2015
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*mangle
:PREROUTING ACCEPT [2424:210831]
:INPUT ACCEPT [2424:210831]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [1856:540218]
:POSTROUTING ACCEPT [1856:540218]
COMMIT
# Completed on Fri Dec  4 04:30:56 2015
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [581:184073]
- -A INPUT -i lo -j ACCEPT
- -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9052 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9051 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9001 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9030 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
- -A INPUT -j DROP
COMMIT
# Completed on Fri Dec  4 04:30:56 2015


> 3:/etc/network$ cat interfaces # This configuration file is
> auto-generated. # # WARNING: Do not edit this file, your changes
> will be lost. # Please create/edit /etc/network/interfaces.head
> and # /etc/network/interfaces.tail instead, their contents will be 
> # inserted at the beginning and at the end of this file,
> respectively. # # NOTE: it is NOT guaranteed that the contents of
> /etc/network/interfaces.tail # will be at the very end of this
> file. #
> 
> # Auto generated lo interface auto lo iface lo inet loopback
> 
> # Auto generated venet0 interface auto venet0 iface venet0 inet
> manual up ifconfig venet0 up up ifconfig venet0 127.0.0.2 up route
> add default dev venet0 down route del default dev venet0 down
> ifconfig venet0 down
> 
> 
> iface venet0 inet6 manual up route -A inet6 add default dev venet0 
> down route -A inet6 del default dev venet0
> 
> auto venet0:0 iface venet0:0 inet static address 167.114.35.28 
> netmask 255.255.255.255

> cat sysctl.conf

> # Uncomment the next line to enable packet forwarding for IPv4 
> net.ipv4.ip_forward=1
> 
> # Uncomment the next line to enable packet forwarding for IPv6 #
> Enabling this option disables Stateless Address Autoconfiguration #
> based on Router Advertisements for this host 
> net.ipv6.conf.all.forwarding=1

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWY4QyAAoJEJQqkaGlFNDPpiEH/jpcbG8GurVjOsSDneOQvKU3
o9cY536TmP2J8+t+JgTfG5KVm/lL1jzBT6/NE62xkWMPrrrdRGx4mLLJJ+AKjTdJ
t+89gBgBdtBfaWtGu29XcgXh/wbWB9EDMZgkKi2iSh9CEVMC5uTZKPXtzslUl6Rk

Re: [tor-relays] Unbelieveable

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 9:29 AM, AMuse wrote:
> Looks like you got more than you paid for.
> 
> 
> 
> On 2015-12-03 18:46, Kurt Besig wrote:
> 
> That I got two responses after posting to tor-relays regarding a 
> fairly simple, I thought, CntrolPort question on a new VPS relay.. 
> That's pathetic. Thanks for all your input.
Yeah, that's the kind of useful answer that has made this list so
popular...thanks for the response. >>
___
>> tor-relays mailing list tor-relays@lists.torproject.org
>> <mailto:tor-relays@lists.torproject.org> 
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYdmyAAoJEJQqkaGlFNDP8D0IAL8sX+r3T6QUKIMP/+fKKgF3
CVARI2JMo6LN2/WTdPvZxe7Bky1d5zfWqkicLzjVTbY8E9O1EsCd1ZIvNAYIDp82
UfFo4hgBxT0aFTd6ViXIbBTBMifszN4/XRlhg8U4wuNKUlSE9tIPODCSC4Pm645A
+vLBMO9nmsiZiAhSUrqF2lqViobL/aj1FR6nShi8GTN/JMc/udHYevi5GT4BRW/0
VTIta2Qz9JU+OUb1dTYvr/K43yotPleQXttt4uyWnBzFVFfRQ8JQ1uG/TL4mm3Eg
AeRoLSHryN/X5UhEtyLuN78uQ53FCDLaun9n5ZzXPeWA62Dyjzb1SNZixRiBn20=
=W5X6
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 10:33 AM, AMuse wrote:
> Believe it or not, Kurt, if you'd asked in your follow-up in
> anything resembling a nice or appreciative tone, I'd have helped
> you.  I'm on too many email lists and things get buried sometimes,
> so I didn't see any of your original requests.  I had a few minutes
> today where I could have chatted with you on IRC and worked things
> out, maybe.
> 
> Instead I gave you a pithy short reply, because that's all your
> attitude deserves.
> 
> Take it as a life lesson (or not, I don't really care that much)
> but you'll get a lot more support from people if you don't act like
> an entitled jerk who deserves other peoples' time and expertise for
> free.
> 
> 
> 
> On 2015-12-04 10:21, Kurt Besig wrote:
> 
> On 12/4/2015 9:29 AM, AMuse wrote:
>>>> Looks like you got more than you paid for. On 2015-12-03
>>>> 18:46, Kurt Besig wrote: That I got two responses after
>>>> posting to tor-relays regarding a fairly simple, I thought,
>>>> CntrolPort question on a new VPS relay.. That's pathetic.
>>>> Thanks for all your input.
> Yeah, that's the kind of useful answer that has made this list so 
> popular...thanks for the response. >> 
> ___
>>>>> tor-relays mailing list tor-relays@lists.torproject.org 
>>>>> <mailto:tor-relays@lists.torproject.org> 
>>>>> <mailto:tor-relays@lists.torproject.org 
>>>>> <mailto:tor-relays@lists.torproject.org>> 
>>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>>
>>>>> 
___ tor-relays mailing
>>>> list tor-relays@lists.torproject.org 
>>>> <mailto:tor-relays@lists.torproject.org> 
>>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>>>> 
___
>> tor-relays mailing list tor-relays@lists.torproject.org
>> <mailto:tor-relays@lists.torproject.org> 
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> 
> You're right, I have been too hasty in my negative responses
to this list's subscribers. For that I do apologize to everyone. I too
am nothing more than a volunteer relay operator like most here and as
such have no special privileges or power to "force" anyone's response.
In  hindsight I realize that. Unfortunately living in this fast paced
society of entitlement it's easy to occasionally get caught up in it,
again, for that I am sorry.
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYd14AAoJEJQqkaGlFNDPSZIIAMPMhePI3zEdxEbeAH7g7SWB
tAsMyesHOfSu4T8m1pHK/ia/fYfIbEBsMhrRPSvjJGJi6qtVRflcMtScvsxRJ49g
4lv5KAcZfUx+coT3XAzK2Cv69LADNsME0sJLME8STH3ZHszo48T4Uv3ZV3hZQuSv
K5cUQ8OHyradfTVHjLQYXSJmjlVRvpqUfN2ingUX8f4Z52K9onT/rVvLjlHoj7iS
/2euRiIGAoNgn7qriaG9hOIMgCg/CChw1CD1lQ4zj/hPKd8cqisD5SGpmPvVMP7j
iRcWh1hFR+7aklJXBr3+3qWUM5WGpDzqc885rLSecSZIt6PJBJVgdagBW+UOXeU=
=zaHm
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS Connection Refused

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/3/2015 7:04 PM, Tim Wilson-Brown - teor wrote:
> 
>> On 3 Dec 2015, at 09:44, Kurt Besig <kbe...@socal.rr.com 
>> <mailto:kbe...@socal.rr.com>> wrote:
>> 
>> After setting up Tor and tor-arm on the VPS I'm not able to
>> connect with this error: unable to reconnect (connection refused.
>> Is the ControlPort Enabled?) I've edited ~/home/.arm/torrc and
>> /etc/tor/torrc un-commenting the ControlPort 9052 and all the
>> other typical ports, etc..
> 
> I don't have enough information to be sure what's going on:
> 
> What control port is tor actually connected to? (Try "lsof -p
> " or "netstat")
> 
> Can "telnet" or "nc" connect to the port?
> 
> Does your VPS provider block connections from localhost to
> localhost by default? (This is an unusual config, that may be why
> the advice you received didn't help.)
> 
> What else have your tried?
> 
>> Obviously I'm not able to forward or enable ports on the VPS, so
>> do I need to ask the admin to make some changes?
> 
> Possibly. Some VPSs let you modify the firewall settings yourself.
> 
> Tim
> 
> Tim Wilson-Brown (teor)
> 
> teor2345 at gmail dot com PGP 968F094B
> 
> teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F
> B5A9D14F
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Thank you Tim for an intelligent response, I'll look into your
suggestions.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYQygAAoJEJQqkaGlFNDPHXIIAIFzYAr7AASz9ZE+IRPL2Xbe
2Rh+TOkFEuwzEtE1YlKUuhqKw03zLgwGyBLJ2Qr0QWAofKvuQVDD0xcR7TPKI/th
LGMwFKpkmCHj4RnYkHAqwVqczPBShLnCtIrLP1JXgAPwFGl14VGodPRRHBYcw7Oh
TNdtgp4Vvx/CL5OyxacoZO4pHIfs4txfx/etYlYd6eYdEJBCm5JxBgJiOLyBdbO9
Se27CW4KqfXy+wxYwz72LUaGyxUnvJ+u6EFAyrZ9KIq1fh/4XDyB6O361hMYl9Na
p5INecLGnBIyA3cBZOq28IqZlAu9dNJSlJSU9x7pO0QetVFHpNOte9DVM5A40Mc=
=gkcJ
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/3/2015 7:11 PM, k0nsl wrote:
> Hi, It's difficult to nail down without any actual information to 
> go on. It's sort of like saying "my back hurts" and asking people 
> what may have caused it to hurt. You'll get a few random answers, 
> at best. -k0nsl
> 
> Den 12/4/2015 kl. 3:46 AM, skrev Kurt Besig:
>> That I got two responses after posting to tor-relays regarding a
>>  fairly simple, I thought, CntrolPort question on a new VPS 
>> relay.. That's pathetic. Thanks for all your input. 
>> ___ > tor-relays 
>> mailing list > tor-relays@lists.torproject.org >
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >
> 
> -- This e-mail message may contain confidential or legally 
> privileged information and is intended only for the use of the 
> intended recipient(s). Any unauthorized disclosure, dissemination, 
> distribution, copying or the taking of any action in reliance on 
> the information herein is prohibited.
> 
> 
> 
> ___ tor-relays mailing 
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Well. even a doctor would make a few suggestions based on some sort of
experience based reasoning. Perhaps some connection problems
associated with running tor-arm on a VPS vs. a home server...things of
that nature. Also I was just wondering as I don't see many of the
relay operators that used to post to this list around anymore, has
something changed to make them move on??
Lots of people whining about their consensus weight numbers, but
little of substance being posted.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYQv1AAoJEJQqkaGlFNDP4d4H/iSOTYsEa3Q+Kj5BIREOY+Ka
KsoplgYbVPbUxg9x37BD88p7+02YMKlwhEW5sMemd/+ySC9IsXhsdfxXrRaE+SZk
tm6+Wd2FoZBDoYem5e87PNo1fBuOE4aBgS3XNBuA2H6FZRpNpY8asOB4YlJdxy66
83aTDB43gRqkHpONgyBcYnhOuOt6L9CiZyXkJqtLpgYAtvmwv82MRYMU72PHsLjE
Dzh+tj4o+FnsDVgC5nnk4yPXyeStMMQLdx51IuamTvji7n/JJD+HQmc94wTq1ocI
AW3GCoeAId7XNtpkVgtfT1lVIS8D177edQHbGAjSIEEE3E+QVhizvSWtBU1i13w=
=/kbu
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Unbelieveable

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

That I got two responses after posting to tor-relays regarding a
fairly simple, I thought, CntrolPort question on a new VPS relay..
That's pathetic. Thanks for all your input.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYP6FAAoJEJQqkaGlFNDPTCUIAKGRC9/XUKeBLrhIlXUrZd03
oTiWdNJebmCRJ55gXbXv+2VxwM18YipkkwEIRmxrSdUsvzn2zRZ11FOnv1Yi8tFY
oiD8HgqLVe6pcDepslPPe/SJyMz6tIqBnosYG6yADOpYCXRR22ehRlPQHkdg2kZ+
ePBWJwDVop8WXUDwgAxRFd/jp/WWjLRt90bgHpcupEzbGi7GMTvNbftHEBeJvhwc
g1xp5gZlvBgCT8Kb03dXQCUaYQ8hpjc9zbo4sQwnJNOZpyU6ftLdsoODa8NRW73s
bslUj6EjQ5P2+tC2d9Q7s669XpLoxipJm1QiYVqFPIfLo48F4GjW1r64SKBxHVw=
=mddV
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] VPS Connection Refused

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I just set up a VPS on PulseServers as I noticed quite a few running
relays had mostly good things to say about the service. So Far the
people operating the servers seem very cooperative and responsive.
Anyway I've been running a middle relay for 1.5 years and know the
"ropes" pretty well, however a VPS is new to me.
After setting up Tor and tor-arm on the VPS I'm not able to connect
with this error: unable to reconnect (connection refused. Is the
ControlPort Enabled?)
I've edited ~/home/.arm/torrc and /etc/tor/torrc un-commenting the
ControlPort 9052 and all the other typical ports, etc.. Obviously I'm
not able to forward or enable ports on the VPS, so do I need to ask
the admin to make some changes?

Thanks
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWX3RnAAoJEJQqkaGlFNDPiS4H/2g/stKLNl0R1ZzbM2/MmC45
D0t2K8E7mcuIhxDiQJ/klaluJWnTHUrUPonSXTZuMYQJOBjdQIV6Mbq61/2g/TK9
VOdiTIsJSD30wmPIUZXlFb7xGX98DNedsySbCG4evJGmJvmEKXiAwg9i/K0iz5Ar
KmRTRxtqCUJcmS+L0s0chV2A7TsIpP2h/WUS/tzc+AmAlbx1jZ4K1zu2uzCqZIjQ
69nkbbHd9DDlmSXvC9aKCB1MO3HcJUgA6gUin4UBOhkrTokbfRQBtizuHqlI4RSG
sL9CyOocs9d1DEQVF1pN3PPNjWh/Owm4WzMTm3dMJ+DuRQQ5ls3R+4Fn9I//2Mg=
=26fO
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS Connection Refused

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/2/2015 7:09 PM, Michael McConville wrote:
> Kurt Besig wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> On 12/2/2015 3:06 PM, Michael McConville wrote:
>>> Kurt Besig wrote:
>>>> I just set up a VPS on PulseServers as I noticed quite a few 
>>>> running relays had mostly good things to say about the
>>>> service. So Far the people operating the servers seem very
>>>> cooperative and responsive. Anyway I've been running a middle
>>>> relay for 1.5 years and know the "ropes" pretty well, however
>>>> a VPS is new to me. After setting up Tor and tor-arm on the
>>>> VPS I'm not able to connect with this error:  I've edited
>>>> ~/home/.arm/torrc and /etc/tor/torrc un-commenting the
>>>> ControlPort 9052 and all the other typical ports, etc..
>>>> Obviously I'm not able to forward or enable ports on the VPS,
>>>> so do I need to ask the admin to make some changes?
>>> 
>>> The arm process needs to be either root's or _tor's (assuming
>>> that the tor process uses the _tor user). It's better not to
>>> use root, as it's unsafe. So, this will likely work:
>>> 
>>>> sudo -u _tor arm
>>> 
>> I use debian_tor as my tor group, but I don't think that's the
>> issue.
> 
> Did you try it (sudo -u debian_tor arm)? Worth a shot. 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
That's the cmd that leads to: unable to reconnect (connection refused.
>>>> Is the ControlPort Enabled?) in tor-arm
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWX7QPAAoJEJQqkaGlFNDPMo0IAKYdvEgL6fcHcIQrGYC5oc7R
D4GefJbOftLC6KmU3kuNn+i5EDB0uFPSkAm2NJWlOjgVRyzAEG3ja95coVLOmyk+
bkWY7sUATr0I9UFWuB8Sh68eg8/SHUinZbso2v+7vK0CuGE2qDDRoq6foxOs3SHv
UAzKmjqPMtawYNL0d0f9rbAEflyXNrIS3o/FoKS91js9L3c0voIRvWc/hCWVAYQi
PqDmWa99yFyfRcNefLMxq8IOTktY4QmdPy0cQNzO5gskBmTX+y1wYvaRMJQxbEsZ
atkuajr3Nhrua2fzQ6rrE3aTCdcsvnEbSPiF6D+u8yeWPNuL75YqGNRaLMT0HX4=
=W6f5
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS Connection Refused

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/2/2015 3:06 PM, Michael McConville wrote:
> Kurt Besig wrote:
>> I just set up a VPS on PulseServers as I noticed quite a few
>> running relays had mostly good things to say about the service.
>> So Far the people operating the servers seem very cooperative and
>> responsive. Anyway I've been running a middle relay for 1.5 years
>> and know the "ropes" pretty well, however a VPS is new to me. 
>> After setting up Tor and tor-arm on the VPS I'm not able to
>> connect with this error: unable to reconnect (connection refused.
>> Is the ControlPort Enabled?) I've edited ~/home/.arm/torrc and
>> /etc/tor/torrc un-commenting the ControlPort 9052 and all the
>> other typical ports, etc.. Obviously I'm not able to forward or
>> enable ports on the VPS, so do I need to ask the admin to make
>> some changes?
> 
> The arm process needs to be either root's or _tor's (assuming that
> the tor process uses the _tor user). It's better not to use root,
> as it's unsafe. So, this will likely work:
> 
>> sudo -u _tor arm
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
I use debian_tor as my tor group, but I don't think that's the issue.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWX6pnAAoJEJQqkaGlFNDPMMwH/2j2BcGprDhSpltVoi2w05Ya
ZhltimSyg0LmESJaKNLn76ElHk09ZpYbzCfesA1264UhWo+nixGptM2HhSHOUui4
pYV4Yd0XJ7OX6ZpsrJJQnf5s1gWTT72bDagDbomqO25WaNaQWuXvgDqbrMaRbWlS
3oPQ43QRAnyZgcLCx/0YXuv3gd5/XxQ01tMQc3O0Ac3ItN5ol9K5viL1FdNIgqHl
QJHYbEAaMpfKnZWyi4zXn/ekBAt+eTzGswLCdY81+3UwTMZwU807M3H5uYdM6zoD
H76oaAOx3KOhTX+/L2MySuzvhr60Udv78exTkWbaPz8B1WQxGExjvlEh+SMxClI=
=rBwb
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS Connection Refused

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/2/2015 4:54 PM, I wrote:
> Doesn't Arm look for 9051?
> 
> Robert
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
By default, but it can be any port you edit into the rc.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWX6oXAAoJEJQqkaGlFNDPROoH/RYpXB3sMwhxLsZDQp5Nn3Nz
os8WkKC5Xw7mzL7ooDo4EOGDVZmHNKW8IUaVXb6ETdZRtnGlm4I/SR1upmE4mpFJ
UwldWwfVCW0khERk08O/MqX0ufIzEH75mmhncs+YcEtzWhjo1mhEISkFC5+3UMXE
OLRSg5jcJyLHBkXweqtU1/B9VB3IpP/OgLviq9ItQ2cNHHlD6Ow3YK373Lm9g9Q6
b7gaD8XlxafH8JVlq5YA/JoypRRi5RoXglPKipmeDrgVgriftl5RB/qlCpR0Dbhw
SE/PKSjA6U5L7S9WpXjp3y33pl2V5eXRPpBqR7bXXK7dwgeSKZG8X8onXJQFnkA=
=rpod
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor Weather not working?

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/20/2015 10:41 AM, tor-server-crea...@use.startmail.com wrote:
> whos then receiving home-addresses from longtime relay-owners
> earned t-shirts?!
> 
> 
> Am Dienstag, 17. November 2015 21:00 schrieb nusenu 
> :
> 
>>> 
>> 
>> tor weather hasn't been working for me for a long time and AFAIK
>> it is not maintained... 
>> ___ tor-relays
>> mailing list tor-relays@lists.torproject.org 
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
I received a T-shirt approximately 4 months ago..
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWT2wHAAoJEJQqkaGlFNDPGJsIAJKKxW8t8xarLinZXLLyUILc
s4EslyACidcubkY3KI27pypJS6IH7Muslg69JQinEC7ns2YVqNPgQK02TjHQUOUi
9PB5StgF53U4w5CBXfPYZkfJeXTH385WR33PwPBgSG/SrT38+FxfY3Yq9Q2q5Via
V48ui8RjLdL2xjkUCm0kEte1vgoXWgXwYqB0Zh5pBL68Gf+YBcWp3Jn0Ri604ILJ
gv+S4YaAisBkg6P1SlgClcZ2W0v7vVzgfnUULiVhftdp3bZpwfh/JnhVsuhX6a0z
XXPsLOKH5fAjEmzwO/YhE6Nmq3GjfG0DNnsc7X5avdijV2skP/yjA91Fk4xTQzU=
=ZUJf
-END PGP SIGNATURE-

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] I.P. being Blocked?

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Without going into any detail at this point I'm wondering if others,
running a simple middle relay, have encountered  any governmental
harassment as a direct result of running a relay. The blocking of
state agencies e.g, CA.SDI.gov, CA.DMV.gov?
 Over the past month I've noticed regardless of which browser, machine
on my LAN, and wired or wireless connection utilized it's become
impossible to connect to any ca.gov site. I've researched my router,
cable modem, and firewall settings, all appear to be fine. Spoke with
my ISP, for whatever worth that might have, and was assured no
blocking or filters were in place that would keep me from reaching
these services and my settings looked fine from what they could see
from their end.
 I'm able to connect to ca.gov sites using my phones 4G network or
through Tor, however for some reason my home network and associated
I.P. is poison.
Any experiences/input would be appreciated.

Thanks
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJVx4UrAAoJEJQqkaGlFNDPILMIALq/zYHqdm/QpThUI/vbr74L
Q5lzLiVJBbxOxC3nWX/fuJL35FyS2FwOY4K+piI0EcDpY+wZ/m2hZh7wJLzwh9ok
z0j0Dcp7GL3N2c64UP/7XFCrlaNtMm/0ke1xsxUkd0NahZNDCqv7BOkR9IX5yAfx
lK5qOw9fpjyzVIdLd1LM1VArWGoEI6dR8PI3rmmGmzP6m9OGC8MxqW2rx+g1p0C5
0F+wDgnmM9rUa2VcgGXf7F4lJkEpUOtjwrsrasclLE8WbwBVv47a84eSSCLKCnUm
rD5fUjFBgcaJtrVRgrwydWBcCuIujfxyiCz+Ku8+jtazB5cMdeiZjZN1pgRgKS8=
=z1cc
-END PGP SIGNATURE-

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] I.P. being Blocked?

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 8/9/2015 10:00 AM, Zack Weinberg wrote:
 On 08/09/2015 12:52 PM, Kurt Besig wrote:
 Without going into any detail at this point I'm wondering if 
 others, running a simple middle relay, have encountered  any 
 governmental harassment as a direct result of running a relay.
 The blocking of state agencies e.g, CA.SDI.gov, CA.DMV.gov?
 
 Are you running a relay on your home network connection?  That is 
 discouraged for a whole bunch of reasons, one of which is that
 several this IP is a source of spam blacklists indiscriminately
 list _all_ Tor relays, whether or not they are exit nodes.  This in
 turn causes random websites to block non-Tor access from the same
 address. California's government website maintainers are probably
 subscribing to one of those blacklists, and that's probably out of
 ignorance rather than malice (the blacklists in question bill
 themselves as more comprehensive than others).
 
 zw
Yes this is a middle relay, on a home network,  I've been running for
approximately 1.5 years with no issues. Since this is a middle relay
and find I have no reason to hide my intentions
there hasn't been an issue in my mind regarding running a relay on my
home network.
  ___
 tor-relays mailing list tor-relays@lists.torproject.org 
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJVx4xYAAoJEJQqkaGlFNDP6j4H/1MTp8vS5BtiTAyhfrXfaCe/
t1YBihtJnK/haZ1zDQ8lPp8zjHYWE/0B8/VoTWVh2jEY7aq8UC27zpdiDHzADPqD
BOelZyK5Ig1+HAdcwSRaRz5nJ891Icmyj8aURdWz6103IK8yMc2bw5s2dcEUq3TG
qLGJ9dKBu7Pl6FIdlrJfs/M104RQuCKhrz1LRMWQFmsUC19AHHHONnguNwv18/nR
wzM4C49s+7BwXlQkvptAlyzF8b5lHhtMin8YBtVMXLKlbFNFwd5Ii8etFMIam9ai
3J2A+C3LS34DAsA19JS1pA2Ekj8P/OU6cel0MsDph2jXNTDU2z85Bn4JDa/1w70=
=fx4x
-END PGP SIGNATURE-

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] New Arris TG1672 Cable Modem, relay not reachable...help!

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 1/19/2015 10:45 AM, kbesig wrote:
 
 On 01/18/2015 02:18 PM, Kurt Besig wrote:
 I'm trying to narrow down my connectivity problem and am
 wondering if anyone is runniing a relay, or knows of someone
 successfully running a relay, that is currently using TWC's new
 Arris TG1672 modem.
 Thanks ___ tor-relays
 mailing list tor-relays@lists.torproject.org 
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
 
[Solved]
After more research I found TWC's new Arris TG1672 modem must be set
to Bridged mode to allow for port forwarding, problem solved!
when I called tech support they did want to know why I needed to
forward ports and acted slightly suspicious,but after I told them I
run several services that need forwarding they where fine with it and
didn't ask for any specifics regarding my services.
Thanks to Sebastian Urbach for all the help in pointing me in the
correct direction.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUvV52AAoJEJQqkaGlFNDP03cH/A9EhZ+gEx7Y/TXTJzDTetK1
QgMyJ82+fZI2kYtxJ2/Yh0yWSTGFjxnH//QYXnBtd/BW1UhNajZjJy5woavpJdjO
d9X9RFa6NCYPachTiYMBIIvxOcqEqweFSt4THIHSJL2LWl2uxKrO7Y+ZGfHF2n5Y
dvwUiGfI/4gUKPAh82Ihp1FADTHMxm89X4Yia2n2WwXKt46upVK+b/1vIekj6q3m
uZTNKqUOiY8X6ESVgC2TZ5DG9Y2LnnYccu5ydXXJGiJ1CMWIBw/rjROoCEBLXsXb
Udw0zemHocB4HqcpalLHzX+9Eekv5OtSi41bUobRBzWfS6etniVfR2EwKceSI+k=
=mXqv
-END PGP SIGNATURE-

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Unexpected sendme cell from...

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I this was discussed awhile back through the mailing list and online
to some extent, however I never grasped the solutions or any real
resolution to the issue.
My relay is getting fairly hammered daily and I'd appreciate any input
regarding the, [WARN] Unexpected sendme cell from client. Closing
circ (window 1000). error message.
Horizons3

Thanks
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUVSJWAAoJEJQqkaGlFNDPKbcH/jZ1H4IAmNZ0PHUHIEvisBJJ
oSHPQ6fgmtAHwdo6uJakc5L+f4aeIZrOfCKWQ+cQ/LxkcWmZs7H/0N4w/PV8mJWV
xN0lPAso9VZLulLuHhLbIJrq6G2XJ1zmBbkmLrEGhT1ZAvFhjcFtwsVTsB0h52EO
da2NWvMpNFESkznkvPZSVa7zIRk4nM4YIdb0jrMa1Jw+Z/JdhfE4IJZ2sCgf9HRu
1fX0318uL1AEN9KKYU4yxwZnboEoyluGALy42e7oGxHryctOHmez0MjXglA2j0BA
4VakJJfF8A4BTkGEzMhi4laDDh1glkRal8nJRONsBlTCulzqEMCCNSLml+Cw6Po=
=PQab
-END PGP SIGNATURE-

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Why did my relay fall out of the consensus?

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 7/4/2014 7:06 AM, Steve Snyder wrote:
 On June 9th my relay, which was established about 20 months ago,
 fell out of the cached consensus.
 
 There are no errors in the logs, just notices that the relay is not
 in the cached consensus.  Apart from upgrading to Tor v0.2.4.22 3
 days earlier I haven't made any changes to the server.
 
 Anyone know what's going on here?
 
 https://exonerator.torproject.org/?targetaddr=targetPort=ip=5.9.191.52timestamp=2014-06-09#relay

 
 
 Thanks. ___ tor-relays
 mailing list tor-relays@lists.torproject.org 
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
 
Your OpenSSL is current?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTtsN7AAoJEJQqkaGlFNDPvkoH/RgEM+MhqW3hxoaZpeoPua1T
mKe/hxmgOC/JnMpoAvQ7ag4agjFR5RndMJaTJKS980m+/y9Jg4HCaVAw/obI9Vd2
m6H/IYNYaJZJm7w4zFQgydLq/2thyhnMc5U0U77GuhbTwC0s2O1AKAv5zippebta
of1a7wPeBBxJqklL0dvuGKr/plXWlTfDHeIE1pGeqhH9Zh3+cyrv69oYSoue7zu8
Ng1/r3eB0sAGpoxKkjFbvHK/XWkTgtviFXeHhVJ5showWT4cmmTa+n+YVXQANNQj
XbcnITJIArLa+/fTIaLNhsggNBj7er/PvxlpFJQxwAhRyN0ZbC8UdUUzAFWoGak=
=xvNz
-END PGP SIGNATURE-

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor-relay - IP

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/18/2014 8:54 AM, Rui Branco wrote:
 hello, I'm a new user of the Tor-relay and I have many doubts.
 Sorry about that.
 
 In the atlas project why the tor-relays ip are discovered? isn't
 it dangerous?
 

When I first starting using Tor and later becoming a relay, I also had
the same fears. However, the correct way to think of a relay's
anonymity, or lack there of, is that being honest and open is really
the best security of all. I have nothing to hide therefore what have I
to fear??
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTodofAAoJEJQqkaGlFNDP0xEH/0w1BoVoaiVeN4pGBO7K3TFt
X41sYQM49NkrbbJ60YoeGWCQqgl+cd9ZTJd4sAJSxFN6Ssj2gdy0XbEuhRyDF7cu
dSNxx7rGiU9X9oyVwUSXAb5fKnQIxIAkOQStzaQXZHUlVpDAVY4ojvo4S7BMi/Co
2UIK4cpGCv/4twVNiFdAYuoAOPV7gGp2RHOGHyjvwg7ofsXPvGNPtJ/lEOlENSDl
RZPdtTdOliSBCP5WvYjJDULAhqM2Mnba/lKITT3pXKpUVLt/chRYOqHa9qMNk4Gq
d1xOsdjFr4ZcPemdBvSD6ZeZBVdURBM2e5oncu6E35eUQndkE6QKWwDGem15VtE=
=ddTN
-END PGP SIGNATURE-

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] SSH scans from Tor exit

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 4/30/2014 9:01 PM, I wrote:
 The original point has drifted over the horizon.
 
 I asked what could be done, in my case, to stop SSH attacks
 originating FROM my VPS which is running as an exit. There was
 another VPS emanating SQL injection attacks.
 
 The problem is that volunteering a cheap VPS to run as a Tor relay
 or exit is a very fickle process. The VPS businesses don't waste
 time on anything to do with them. Their reaction is nearly always
 absolute.
 
 It would be smart for the Tor society to approach that situation
 with guidance for ordinary people to successfully get another exit
 or relay running most of which would have to be on VPSs to get the
 speed and volume.  I know there are bits and piecs on this subject
 but they are not a coherent guide for ordinary people.
 
 Robert
 
 
 
 
 ___ tor-relays mailing
 list tor-relays@lists.torproject.org 
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
 
Your points are well taken, Robert. I'm a relative newcomer to running
a relay so unfortunately don't have the answers you seek, however I'm
in agreement that more help and less bashing is in order if the
bashers want to keep Tor alive../mini-rant
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTYlFoAAoJEJQqkaGlFNDPaH0IALEBZd4RgcvdJt1z4HnyIYIk
Imw71M+WUyg88wr/DDS8JBRrjw0SXIcgGiMn+fGm4xVHyAqumFcxukupWCrozqPt
YI1M/pcmgl5ZBgjFidOAxKYDBk7mfQ+qkBL9fCg7XsHNJZVnppxisQMADN6T3PhZ
l8HntabRSm0fH/cRJYVaCrsAoLxclChA/N179sEa19U1gyCbftpxwi4UzdY5Ttbn
z25eKgNSFwtYz4DEFkf9MB5MLzDjbXiV/RG6gghHUvBzjCabV4DCM9zlwXBEv8Sr
dG1As2GIgLz6dIs6KaDTHdd03xbxOqzps072JW83mJ8tZl7RSkbEZeErLTOpT2s=
=H+C/
-END PGP SIGNATURE-

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays