- tor-relays - lists.torproject.org

Running relay on vmware ? is it secure to use Tor on virtual systems ?
by dlugasny＠protonmail.com 02 Nov '18

02 Nov '18

Hi, is it secure to run Tor Relay / Tor browser on Vmware ? On my Windows 10 desktop I have installed VMware Player where is running Ubuntu. I`m using that system to browse internet using Tor Browser. Is it secure to use Tor browser on virtual systems ? Cheers DLugasny

2 5

Re: [tor-relays] Running an exit node from home
by Isaac Grover, Aileron I.T. 01 Nov '18

01 Nov '18

Good morning Spiros, You are correct in that I won't maintain the exit flag without ports 80 and 443 open, *and* I lose my eligibility for a free t-shirt, *but* I am not likely to attract attention at my home either. =) Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - "Practical & Proactive I.T. Solutions" O: 715-377-0440, F:715-690-1029, W: www.aileronit.com LinkedIn: https://www.linkedin.com/in/IsaacGrover/ YouTube: https://www.youtube.com/channel/UCqrwZNFKdR-guKtuQzFPObQ

4 6

List purpose and moderation
by Colin Childs 01 Nov '18

01 Nov '18

Hello tor-relays, This message is to make everyone aware of the purpose of this list, and to notify that off-topic posting will result in moderation. This is to allow the list to continue being used as a relay operator support mechanism, and to make sure the people on the list for this purpose are not driven away by off-topic posts. The stated purpose of this list is as follows: Support and questions about running Tor relays (exit, non-exit, bridge) Topics relating to this are encouraged and accepted on the list at any time. However, this does not include: Posts intended to troll / annoy members of the list Acting as a support, publicity or communications channel for specific hosting providers Posts regarding general tech news of the day The tor-relays@ list is primarily a communication forum for current and prospective relay operators to obtain support, plus share stories and experiences. Relevant discussions about specific providers are also germane, although any usage of this list for the purposes of publicity or as a communications / support channel for providers is prohibited. Thank you all for being part of the relay operator community!

2 1

Running an exit node from home
by Isaac Grover, Aileron I.T. 31 Oct '18

31 Oct '18

Good morning, As a followup to my last (and other) posts on this list, I have been cautioned multiple times of running an exit node from my home. After careful consideration and previous direct feedback from this list, I configured an exit node with the following exit policy, which allows traffic on ports that are "safe" in my opinion, meaning that they're not likely to generate complaints or search warrants. accept *:5228 accept *:8333 accept *:9418 accept *:11371 reject *:* Regarding these aforementioned cautions, they all seem to be based on dated posts and/or irresponsible exit policies. I would not open any of the web, email, irc, remote desktop, ssh, etc. ports on an exit node based at home as those would generate complaints and/or search warrants very quickly, so I am open to discussion about modifying the groupthink behind this blanket "don't run an exit node at home" advice. Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - "Practical & Proactive I.T. Solutions" O: 715-377-0440<tel:715-425-0440>, F:715-690-1029<tel:715-690-1029>, W: www.aileronit.com<http://www.aileronit.com/> LinkedIn: https://www.linkedin.com/in/IsaacGrover/ YouTube: https://www.youtube.com/channel/UCqrwZNFKdR-guKtuQzFPObQ

4 3

Re: [tor-relays] freebsd relay doesnt receive any traffic (after 1 month)
by dlugasny＠protonmail.com 30 Oct '18

30 Oct '18

Hi Matt, thanks for Your hints. To build my BSD relay, I used some of the available in the internet BSD tutorials. It seems that I have copied some parameters without understanding what for they are. I would like to run non-exit tor relay. Which parameters should I commented out ? Documentation, in did I have to read it, but it would be much easier (much faster) to have some example which user can copy with some small modifications. Cheers Dlugasny Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, October 25, 2018 5:11 PM, Matt Traudt <pastly(a)torproject.org> wrote: > On 10/25/18 13:05, dlugasny(a)protonmail.com wrote: > > > Hi, > > few weeks ago ( more than 4) I have installed Freebsd with Tor relay > > service. > > System is connected to Tor network since more than one month but I see > > only 1-2 connections per day. > > I had Tor relay service on my Debian server for many years and I havent > > got any problems. With Freebsd its pain, nothing is working as expected. > > Any how I would like to build more BSD instances in few different > > countries, but first I need to know why its not working. > > Does any one could help me to do some troubleshooting ? > > Maybe some of the parameters in the torrc are blocking traffic ? > > My torrc without Hashedpassword, Nickname: > > ########################### > > SocksPort 0 > > Log notice file /var/log/tor/notices.log > > ControlPort 9051 > > ORPort 9001 > > RelayBandwidthRate 400 KBytes # Throttle traffic to 100KB/s (800Kbps) > > RelayBandwidthBurst 600 KBytes # But allow bursts up to 200KB (1600Kb) > > ContactInfo Dlugas-ny <dlugasny AT protonmail dot com> > > DirPort 9030 # what port to advertise for directory connections > > ExitPolicy reject : # no exits allowed > > PublishServerDescriptor 0 > > CellStatistics 1 > > ExtraInfoStatistics 1 > > ConnDirectionStatistics 1 > > EntryStatistics 1 > > LogMessageDomains 1 > > AvoidDiskWrites 1 > > WarnPlaintextPorts > > HeartbeatPeriod 1hours > > ServerTransportPlugin obfs2,obfs3 exec /usr/local/bin/obfsproxy managed > > ServerTransportPlugin obfs4 exec /usr/local/bin/obfsproxy managed > > ExtORPort auto > > ############################ > > Thanks in advance for any support > > This is a very confused torrc. What are you trying to accomplish with it? > > There's lines indicating you want to run a bridge > (ServerTransportPlugin, ExtORPort) > > There's a line indicating you don't want your bridge to be one > distrubted via BridgeDB (PublishServerDescriptor 0), yet you wonder why > no one is using your bride/relay. > > Please read > > https://trac.torproject.org/projects/tor/wiki/TorRelayGuide > > And don't set any options that it doesn't tell you to set. And don't set > options you don't understand. `man tor` can help you understand what > you're setting > > Matt

4 5

searching the tor-relays archives
by torix＠protonmail.com 30 Oct '18

30 Oct '18

Before I download months of gzipped archives and zgrep them myself, is there a way to search the messages themselves? I'm looking at: https://lists.torproject.org/pipermail/tor-relays/ but maybe there as another setup somewhere else. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 2

Re: [tor-relays] Monitoring exit node traffic by port?
by Isaac Grover, Aileron I.T. 30 Oct '18

30 Oct '18

Good morning all, My motivation for the traffic graphing per port was simply to get an idea if the ports were even being used, and I would only view them internally - would this still be a violation of user trust? Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - "Practical & Proactive I.T. Solutions" O: 715-377-0440, F:715-690-1029, W: www.aileronit.com LinkedIn: https://www.linkedin.com/in/IsaacGrover/ YouTube: https://www.youtube.com/channel/UCqrwZNFKdR-guKtuQzFPObQ

1 0

new log message: [warn] Unparseable microdescriptor
by Toralf Förster 30 Oct '18

30 Oct '18

Get this at my exit relay since yesterday: # head /tmp/warn.log Oct 23 23:30:17.000 [notice] Tor 0.3.5.3-alpha opening new log file. Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor Oct 23 23:30:33.000 [warn] parse error: internal NUL character. Oct 23 23:30:33.000 [warn] Unparseable microdescriptor even with log level "debug" there seems to be no more information. Anything I should worry about? -- Toralf PGP C4EACDDE 0076E94E

3 3

Re: [tor-relays] New to Tor Relay, using Rasberry Pi3. Grateful for Help
by Judd Briggs 27 Oct '18

27 Oct '18

HI Matt and Felix. Thank you so much for the guidance. Matt you are right, I never really asked a question, but I think you have helped steer me in the right direction. Alex: Yes...typo on ORport....will fix that. Log file: Yes, it is in the right location, but crazily just stops....clean stop! Also, I went back and seriously studied the relay page. The RaspPi part is a bit confusing especially now, if Pi3 are not a problem, why does it state there is a problem?. But I understand wtih Pi3, more Debian items (TOR) are stable I will add to my source list Debian location which should allow me to update to the latest stable TOR on Debian. Can I have more than one source in the sourcelist? I had another question about the gg2g key thingy...I can't find the exact place in the Tor website. Wasn't sure where to do apt-get "?what?" Give me a couple of days to get back to you on my progress. Regarding the other question asked...yes, I restated like you posted. In next update, I will provide terminal window information. Thanks and best regards, Judd ************************************************************ Date: Fri, 26 Oct 2018 21:31:57 +0200 From: Felix <zwiebel(a)quantentunnel.de> To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] New to Tor Relay, using Rasberry Pi3. Grateful for Help Message-ID: <5BD36BAD.4010005(a)quantentunnel.de> Content-Type: text/plain; charset=utf-8 Hi Judge The torrc shows 'ORPORT' instead of 'ORPort'. I remember some issues with case sensitive torrc entries. Can you try 'ORPort' ? SocksPort 0 Log notice file /var/log/tor/notices.log RunAsDaemon 1 ORPORT 9001 DirPort 9030 ExitPolicy reject *.* RelayBandwidthRate 200 KB RelayBandwidthBurst 400KB -> ORPort 9001 PS: *Lebowski1* how cool! -- Cheers, Felix ------------------------------ Date: Fri, 26 Oct 2018 08:59:09 -0400 From: Matt Traudt <pastly(a)torproject.org> To: tor-relays(a)lists.torproject.org Subject: Re: [tor-relays] New to Tor Relay, using Rasberry Pi3. Grateful for Help Message-ID: <0736abd6-3b7a-c5ff-a300-da79da2c0ddd(a)torproject.org> Content-Type: text/plain; charset=utf-8 On 10/26/18 08:38, Judd Briggs wrote: > Good evening, thanks for taking the time to help me. > > I am fairly new to Pi, Linux/Raspbian, and TOR. But I believe in what > TOR stands for so I wanted to do something with the Pi I had sitting around. > > [... snip ...] > > Appreciate any help. And by the way, i did go back and look through the > archives over the last several months and didn't find a solution. > > Best regards, > > Judge > Thanks for running a relay! You never actually asked a question so I can only guess what you're problem is and what you're looking for help on. In short, see Tor's official relay guide: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide # Version 0.2.9.15 is part of the LTS release series and is an okay version to be running. If you're looking for a newer version of Tor, you'll need to add the Tor Project Debian repos. https://www.torproject.org/docs/debian.html.en#ubuntu Note that I'm only pretty sure the tor you'll get from there will work on rpi 3. Read the warnings on the page. # Am I running a relay correctly? Your torrc looks correct for running a non-exit relay. The logs you shared don't have the lines that I'd expect for any type of relay. Is your torrc located at /etc/tor/torrc? Did you start Tor via systemd like 'sudo systemctl restart tor' or from the command line manually? Hope that helps. Matt *******************************************************************************

1 0

Restore tor exit node
by node47＠torsrv.de 27 Oct '18

27 Oct '18

Dear all, I have the following problem: My VPS-Hoster has deleted my server. Now I reinstalled tor on fresh Debian 9 minimal in version 0.3.4.8 (as before). I also restored my keys from /var/lib/tor/keys and set the datadir in torrc to /var/lib/tor When I started the tor-service a new ed25519_signing_cert and ed25519_signing_secret_key were generated as well as a new fingerprint. The secret_* files still have the old timestamp but new fingerprint had been created. Now the server is listed 3 times in the relaysearch and my node is known as “new” node instead of getting the old fingerprint and the old flags/status. Who can assist me in how to do the restore of the fingerprint and how to correct the relaysearch?! Best regards from Germany Max

4 3