Re: [tor-relays] Tor Relay Software Warns When Current RunningVersion Of Tor Is No Longer Recommended, But Not When A Newer Version IsAvailable?
Am 21.09.2018 um 00:39 schrieb teor: > >> On 21 Sep 2018, at 04:00, Keifer Bly wrote: >> >> So what would be an advised way to make sure tor is 100% up to date, besides >> the update command? Thank you. > > Since you are on macOS and using Homebrew, you should use "brew update". > No extra steps are needed. > > If you want, you can watch the logs for warnings that your tor version is > not recommended. And you can find the list of the good ones on your pc. All tor instances need a file `cached-microdesc-consensus´. Read the text and find the `client-versions´ line. Currently the entry says: client-versions 0.2.9.14,0.2.9.15,0.2.9.16,0.2.9.17,0.3.2.6-alpha,0.3.2.7-rc,0.3.2.8-rc,0.3.2.9,0.3.2.10,0.3.2.11,0.3.2.12,0.3.3.1-alpha,0.3.3.2-alpha,0.3.3.3-alpha,0.3.3.4-alpha,0.3.3.5-rc,0.3.3.6,0.3.3.7,0.3.3.8,0.3.3.9,0.3.3.10,0.3.4.1-alpha,0.3.4.2-alpha,0.3.4.3-alpha,0.3.4.4-rc,0.3.4.5-rc,0.3.4.6-rc,0.3.4.7-rc,0.3.4.8,0.3.5.1-alpha -- Cheers, Felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Jerk spammers on tor-relays (was Re: Fwd: Tor GuardRelay)
So, for me, it appears that the jerk spammers have advanced, Instead of sending spam to the tor-relays@lists.torproject.org email address, they are now directly sending spam to specific addresses subscribed to the list. I got one today from colemanroset...@gmail.com, and have been receiving some over the last few days that were sent directly to this email address. I did not think they were related, but the other email addresses the one I received today was also sent to the addresses below, which I believe are addresses that are subscribed to the list. I have reported it to Google via their abuse report email address which is registrar-ab...@google.com, so I will see what they say (and forward it to the list if requested). The other addresses were: johndalton...@gmail.com, and teor2...@gmail.com. I tried attaching a photo of the "to" field but it was rejected due to size limitations. Just thought I'd give a heads up. On Thu, Sep 20, 2018 at 9:10 PM Keifer Bly wrote: > So, for me, it appears that the jerk spammers have advanced, Instead of > sending spam to the tor-relays@lists.torproject.org email address, they > are now directly sending spam to specific addresses subscribed to the list. > I got one today from colemanroset...@gmail.com, and have been > receiving some over the last few days that were sent directly to this email > address. I did not think they were related, but the other email addresses > the one I received today was also sent to the addresses in the attached > photo, which I believe are addresses that are subscribed to the list. I > have reported it to Google via their abuse report email address which is > registrar-ab...@google.com, so I will see what they say (and forward it > to the list if requested). > > Just thought I'd give a heads up. > > > > On Fri, Jul 13, 2018 at 7:47 PM Keifer Bly wrote: > >> I looked it up. You can forward the spams that the Gmail address are >> sending to registrar-ab...@google.com, which reports spam emails and >> inappropriate content being sent by Gmail users to Google. Try that. >> >> >> >> *From: *Mirimir >> *Sent: *Friday, July 13, 2018 7:41 PM >> *To: *tor-relays@lists.torproject.org >> *Subject: *Re: [tor-relays] Jerk spammers on tor-relays (was Re: Fwd: >> Tor GuardRelay) >> >> >> >> On 07/13/2018 03:07 PM, Keifer Bly wrote: >> >> > Dang. I stopped getting them for a while due to the SPAM filter I >> >> > configured in Gmail, however they are now coming through again. These >> >> > spammers are trying to be smart by sending these spam messages from >> >> > different domains; they are now coming from >> >> > scarlettsofia710...@it.argmx.com >> >> > >> >> > Anyone else getting these? >> >> > >> >> > Thanks. >> >> >> >> I haven't received those after posts since June 27. And nothing from >> >> *.argmx.com. But I am getting sex spam from a few Gmail addresses, with >> >> blank subject lines. New, and perhaps related. >> >> >> >> > On Sat, Jun 9, 2018 at 10:38 PM Roger Dingledine wrote: >> >> >> >> >> >> >> >> >> Maybe there is a mailman module that lets you send a different >> watermarked >> >> >> mail to each subscriber, or to send mails out with different timing >> >> >> patterns to do a binary search over the list, in order to discover >> which >> >> >> addresses are triggering the spam? But I don't know of an easy way to >> >> >> do it. >> >> >> >> That would be a bad precedent, I think ;) >> >> >> >> >> Also, I hear from at least one person that some tor-dev subscribers are >> >> >> getting spams too. :( >> >> >> >> Searching for the spam addresses, I found reports from other mail lists. >> >> So it's not just Tor lists. >> >> >> >> >> >> ___ >> >> 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
Re: [tor-relays] Relay out of consensus after node migration
> On 21 Sep 2018, at 04:26, T0r-n0d3 wrote: > > I recently migrated my tor node to new hardware: > t0rnod3 5582BBEC12380E34D7DFB8C237939A0B317B205E > > Copying the /var/lib/tor/keys/ folder on the process. > Now my node do not handles circuits, nor it's shown in atlas and I see the > following on the logs: > [notice] Heartbeat: It seems like we are not in the cached consensus. What does your relay log when it uploads its descriptor to the directory authorities? Please restart your relay, and send us your notice-level logs via a pastebin service. https://paste.debian.net/ is accessible over tor, for those of us who use Tor Browser. T___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor Relay Software Warns When Current RunningVersion Of Tor Is No Longer Recommended, But Not When A Newer Version IsAvailable?
> On 21 Sep 2018, at 04:00, Keifer Bly wrote: > > So what would be an advised way to make sure tor is 100% up to date, besides > the update command? Thank you. Since you are on macOS and using Homebrew, you should use "brew update". No extra steps are needed. If you want, you can watch the logs for warnings that your tor version is not recommended. T >> On Wed, Sep 19, 2018 at 11:13 PM teor wrote: >> >>> On 20 Sep 2018, at 07:02, Keifer Bly wrote: >>> >>> >>> >>> A few days ago, I upgraded my version of tor from 0.3.3.9 to tor 0.3.4.8. I >>> noticed, however, that tor does not tell me when a new version is >>> available. But in the past when I was a few versions behind, it popped up >>> with a message saying “WARNING: this version of tor is out of date or no >>> longer recommended.” >>> >>> >>> >>> So, I am just wondering, why is it that the tor software warns when the >>> current version is “no longer recommended” but does not warn when an update >>> is available? >>> >> >>> From: teor >>> Sent: Wednesday, September 19, 2018 5:04 PM >>> >>> Tor only warns about obsolete versions. >>> >>> It doesn't warn when there is a new release or "new in series" version >>> available. >>> >>> >>> >>> Definitions here: >>> >>> https://gitweb.torproject.org/torspec.git/tree/version-spec.txt#n53 >>> >> >>> On 20 Sep 2018, at 12:56, Keifer Bly wrote: >>> >>> So does this mean any version of tor is safe to use as long as it is not >>> considered “obsolete”? Thanks. >>> >> >> Sometimes, a supported releases series will have serious security bugs. >> >> When we fix those bugs, we "un-recommend" that version, and recommend >> the newer versions in that series. >> >> So please don't run "obsolete" or "un-recommended" Tor versions. >> >> T >> ___ >> 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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
Hi, On 20/09/2018 10:37, Ben Riley wrote: > ... I've actually got 4 ports open on the router for TOR - 9001, 9030, > 9050 & 9051. > > I set 9030 as my control port in torrc - does that port need to be open > on the router? ... You probably don't need or want either the control port or the SOCKS port open on the router. The control port is normally used to allow "front end" software like Vidalia to connect to the node and get diagnostic information, change some configuration settings, tell it to do things like build a new circuit, etc. so it only needs to be accessible to machines from which you want to manage the node in this way. If, for some reason, you did want to manage the node over the internet, I would recommend keeping the port blocked on the router anyway and tunnelling it through an SSH connection to the server. The SOCKS port is used to tunnel connections through Tor, either directly from software that supports SOCKS, via a wrapper such as socksify or torify or through a proxy server like Privoxy. Again, that only needs to be accessible to machines from which you want to "use" Tor. Again, if you want to use your node as a "gateway" into Tor from elsewhere, you should tunnel the port over SSH. Hope this helps, Stephen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] IPv6 on DSL
Thank you for your hint Ralph - the domain could be spoofing :-), but yes you are right, its non exit traffic. @nusenu: what whould be this list without you - thanks!! > > Based on your email domain and your question about a dynamic DSL link, > I'm guessing you are considering running a Tor relay at home? As stated > in https://www.torproject.org/docs/faq-abuse.html.en : "In general, it's > advisable not to use your home internet connection to provide a Tor > relay." > > -Ralph ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Relay out of consensus after node migration
Hi, I recently migrated my tor node to new hardware: t0rnod3 5582BBEC12380E34D7DFB8C237939A0B317B205E Copying the /var/lib/tor/keys/ folder on the process. Now my node do not handles circuits, nor it's shown in atlas and I see the following on the logs: [notice] Heartbeat: It seems like we are not in the cached consensus. Kind regards Sent with [ProtonMail](https://protonmail.com) Secure Email.___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] IPv6 on DSL
On 20.09.18 16:54, Paul wrote: > Can Tor cope with a daily changing IPv6 Address? Based on your email domain and your question about a dynamic DSL link, I'm guessing you are considering running a Tor relay at home? As stated in https://www.torproject.org/docs/faq-abuse.html.en : "In general, it's advisable not to use your home internet connection to provide a Tor relay." -Ralph ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor Relay Software Warns When Current RunningVersion Of Tor Is No Longer Recommended, But Not When A Newer Version IsAvailable?
So what would be an advised way to make sure tor is 100% up to date, besides the update command? Thank you. On Wed, Sep 19, 2018 at 11:13 PM teor wrote: > > On 20 Sep 2018, at 07:02, Keifer Bly wrote: > > > > A few days ago, I upgraded my version of tor from 0.3.3.9 to tor 0.3.4.8. > I noticed, however, that tor does not tell me when a new version is > available. But in the past when I was a few versions behind, it popped up > with a message saying “WARNING: this version of tor is out of date or no > longer recommended.” > > > > So, I am just wondering, why is it that the tor software warns when the > current version is “no longer recommended” but does not warn when an update > is available? > > > *From: *teor > *Sent: *Wednesday, September 19, 2018 5:04 PM > > Tor only warns about obsolete versions. > > It doesn't warn when there is a new release or "new in series" version > available. > > > > Definitions here: > > https://gitweb.torproject.org/torspec.git/tree/version-spec.txt#n53 > > > On 20 Sep 2018, at 12:56, Keifer Bly wrote: > > So does this mean any version of tor is safe to use as long as it is not > considered “obsolete”? Thanks. > > > Sometimes, a supported releases series will have serious security bugs. > > When we fix those bugs, we "un-recommend" that version, and recommend > the newer versions in that series. > > So please don't run "obsolete" or "un-recommended" Tor versions. > > T > ___ > 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
[tor-relays] More IPv6 questions
Paul: > https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Parttwo:technicalsetup > > uses "ORPort [IPv6-address]:9001" - so can i use the same port number for > IPv4 and IPv6? yes > If I run more than one instance on the same machine, can i use the same IPv6 > address like in the first instance - as i can do in IPv4? yes -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu 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] IPv6 on DSL
Paul: > Can Tor cope with a daily changing IPv6 Address? unfortunatelly the IPv6 address currently has to be in the torrc file, so a daily changing IPv6 address won't be much fun -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu 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] More IPv6 questions
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Parttwo:technicalsetup uses "ORPort [IPv6-address]:9001" - so can i use the same port number for IPv4 and IPv6? If I run more than one instance on the same machine, can i use the same IPv6 address like in the first instance - as i can do in IPv4? "ip addr|grep inet6|grep global" doesn't give an answer on every server - what to do instead please to fill the square brackets? Thanks Paul ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] IPv6 on DSL
Can Tor cope with a daily changing IPv6 Address? If so, are there any additional inputs in torrc to be made as "ip addr|grep inet6|grep global" is not giving a fix value (global noprefixroute dynamic ) Thanks Paul ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
I'm back in business THANK YOU!! So I changed a couple of ports and also opened those on my router. Previously I only had 9030 & 9001. I've added DirPort on 9051, Socks on 9050. I've actually got 4 ports open on the router for TOR - 9001, 9030, 9050 & 9051. I set 9030 as my control port in torrc - does that port need to be open on the router? Or can I remove that port forward? I have one of the authentication methods unhashed, so I believe that protects that somewhat. netstat -tlpn returns the following: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:90510.0.0.0:* LISTEN 9531/tor tcp0 0 127.0.0.1:9030 0.0.0.0:* LISTEN 9531/tor tcp0 0 0.0.0.0:90010.0.0.0:* LISTEN 9531/tor tcp0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 1342/teamviewerd tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 747/systemd-resolve tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 6055/cupsd tcp0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 9531/tor tcp6 0 0 ::1:631 :::* LISTEN 6055/cupsd nyx appears to be running fine now. I can see the graph and log messages like previously. It pulled my previous Nickname, but I currently have no flags, so I'm guessing that will update later. I've got the exit policy set to reject *:* however, as I don't want to blow my ISP off. Is that about it? Can anyone think of anything else I need to check? Thank you to everyone who offered solutions! On Thu, Sep 20, 2018 at 4:19 AM Chad MILLER wrote: > I maintain the tor-middle-relay Snap package. It listens on system-chosen, > arbitrary ports. May be useful to you, itself, or to steal ideas from. > > $ sudo snap install tor-middle-relay > > > > > On Wed, Sep 19, 2018, 04:56 Ben Riley wrote: > >> First off, will outline that I am very much a newbie, but was able to get >> a relay up and running on a Ubuntu machine. It was running fine for maybe >> 12 months (MelbTorBox), with a few resets and software updates along the >> way. >> >> Just doing my bit to help the network. >> >> Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed >> I did it basically the same way. >> >> Unfortunately, that appears not to be the case. >> I've posted the error messages on the Ubuntu forum hoping to get >> assistance, but no joy: >> >> https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bind-to-0-0-0-09050-address-already-in-use-i >> >> I'm now coming to the experts to see if I can resurrect relay before I >> pull the pin on the idea. >> >> I have BASIC Unix knowledge (I can type commands and that's about it). I >> think I might have a couple of copies installed in different places and I >> know I have the TOR browser installed (it works fine). >> >> When I type 'nyx' it replies with: >> Unable to connect to tor. Maybe it's running without a ControlPort? >> >> So I type 'tor' and get >> Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running >> on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma >> 5.2.2, and Libzstd 1.3.3. >> Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! >> Learn how to be safe at >> https://www.torproject.org/download/download#warning >> Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". >> Sep 19 21:34:24.823 [notice] Based on detected system memory, >> MaxMemInQueues is set to 2862 MB. You can override this by setting >> MaxMemInQueues by hand. >> Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. >> Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050 >> Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 >> Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 >> Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050 >> Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address >> already in use. Is Tor already running? >> Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener >> on 127.0.0.1:9050 >> Sep 19 21:34:24.824 [notice] Closing partially-constructed Control >> listener on 127.0.0.1:9051 >> Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on >> 0.0.0.0:9001 >> Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to >> bind one of the listener ports. >> Sep 19 21:34:24.824 [err] Reading config failed--see warnings above. >> >> I 'think' my original torrc file may have somehow survived the Ubuntu >> upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. >> But when I edited it, there were my contact details sitting there. >> >> Very appreciative of any help! >> >> Thanks >> Ben. >> > _
