[tor-relays] (no subject)
Hi. I am from. Turkmenistan. I have obtained obsf4 bridge from internet but only ip address is readable. If anybody knows fully obsf4 bridge please send me to my mail. Ip address is: obsf4 93.104.161.141 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (No Subject)
Hi there, I currently own a Tor Relay that has been running since 2022-05-24. A day ago it restarted, which was a bit strange. Recently I found that the Relay has changed to a Guard Relay, which I am pleased about. I was wondering why the restart occurred as the VPS Server has been online since the first start. The Relay is called UKLondonRelay1 with the IP address 80.64.218.62. https://metrics.torproject.org/rs.html#details/B1B1CAD0A73EC5148B06A0A0E8194C3D0C882253 Any help on this matter would be appreciated. Kind regards, Leon The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (No Subject) (allforprivacy)
Good afternoon, The Library Freedom Project is what you're seeking, for libraries: https://libraryfreedom.org/ Also, I found this response on Slashdot for hosting at a university: https://yro.slashdot.org/comments.pl?sid=7773441&cid=50227785 Make your day great, Isaac Grover ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (No Subject)
Good evening, I'd like to ask: How would one go about encouraging an organization (such as a college, university or library), that they are affiliated with to some extent, to operate a Tor Exit Relay? I currently operate a Non-Exit relay at home, but I would like to also see if me and some others in my organization could start an exit relay as well (Our jurisdiction is the United Kingdom). Thank you for reading, allforprivacy operator.___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Hello dear people I have an OBSF4 bridge to support the free internet. If I look at my bridge via https://metrics.torproject.org/ then the bridge distribution mechanism is set to HTTPS. But I would like to activate Moat. How does it work? Thank you very much ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
as I wrote earlier, they are disconnected arbitrarily for 3-4 hours and then restored themselves, maybe it is better to remove the ports of dir? bandwidth should be enough running on four cores with 4 GB of memory speed 800/800 Mbps 14.05.2020, 22:52, "Felix" :Hi СтаниславYou have two relays running at the same IP. Your IP and relays seemvisible to the network:armik CE5ED345398CC02D573347C2F238F80B18E680EE178.140.230.147,broadband-178-140-230-147.ip.moscow.rt.ru,443,80Fast Run V2Dir Valid bw=9290Fast V2Dir ValidFast Run V2Dir ValidFast V2Dir Valid bw=10200Fast V2Dir ValidV2Dir ValidV2Dir Valid Run V2Dir ValidFast V2Dir Valid bw=7890armik1 0C0388BC552D7AC903F49390A40244FD3FFF44A2178.140.230.147,broadband-178-140-230-147.ip.moscow.rt.ru,9001,9030Fast Run V2Dir Valid bw=4650Fast Run V2Dir ValidFast Run V2Dir ValidFast Run V2Dir Valid bw=3200Fast Run V2Dir Valid!Fast Run V2Dir ValidFast Run V2Dir Valid bw=5960!Fast Run V2Dir ValidFast Run V2Dir Valid bw=6670Fast Run V2Dir Valid bw=4650 bwauth=moria1Am 14.05.2020 um 19:18 schrieb Станислав: hi, I still don’t understand why the relays constantly go offline for no apparent reasonMay-be there are indications: On 4 May 2020, at 20:51, Станислав> wrote: hi, strange but the relay constantly spontaneously goes offline after 3, 4 hours again online in the logs no errors other than this (Failing because we have 4063 connections already. Please read doc / TUNING for guidance. [over 1601 similar message (s) suppressed in last 21600 seconds)and TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters. what it can mean? also my 2 relays go offline for a few hours once a day, then are restored.Port 80 is your DIR port.If you suffer under potential overload or not enough resources (by whatever reason) you can reduce.Run only one relay with OR port only and strict DOS settings. Then waita week if everything works. Wait an other week. If still everything isrunning well add the DIR port again and wait and wait. Add the secondrelay in the same way and finally relax DOS settings.When ever the relay(s) become unstable go one step back.This is a recommendation but there might better ways to go.Good luck! --Cheers, Felix___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] (no subject)
Hi Станислав You have two relays running at the same IP. Your IP and relays seem visible to the network: armik CE5ED345398CC02D573347C2F238F80B18E680EE 178.140.230.147,broadband-178-140-230-147.ip.moscow.rt.ru,443,80 FastRun V2Dir Valid bw=9290 FastV2Dir Valid FastRun V2Dir Valid FastV2Dir Valid bw=10200 FastV2Dir Valid V2Dir Valid V2Dir Valid Run V2Dir Valid FastV2Dir Valid bw=7890 armik1 0C0388BC552D7AC903F49390A40244FD3FFF44A2 178.140.230.147,broadband-178-140-230-147.ip.moscow.rt.ru,9001,9030 FastRun V2Dir Valid bw=4650 FastRun V2Dir Valid FastRun V2Dir Valid FastRun V2Dir Valid bw=3200 FastRun V2Dir Valid !Fast Run V2Dir Valid FastRun V2Dir Valid bw=5960 !Fast Run V2Dir Valid FastRun V2Dir Valid bw=6670 FastRun V2Dir Valid bw=4650 bwauth=moria1 Am 14.05.2020 um 19:18 schrieb Станислав: hi, I still don’t understand why the relays constantly go offline for no apparent reason May-be there are indications: On 4 May 2020, at 20:51, Станислав mailto:armik...@gmail.com>> wrote: hi, strange but the relay constantly spontaneously goes offline after 3, 4 hours again online in the logs no errors other than this (Failing because we have 4063 connections already. Please read doc / TUNING for guidance. [over 1601 similar message (s) suppressed in last 21600 seconds) and TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters. what it can mean? also my 2 relays go offline for a few hours once a day, then are restored. Port 80 is your DIR port. If you suffer under potential overload or not enough resources (by what ever reason) you can reduce. Run only one relay with OR port only and strict DOS settings. Then wait a week if everything works. Wait an other week. If still everything is running well add the DIR port again and wait and wait. Add the second relay in the same way and finally relax DOS settings. When ever the relay(s) become unstable go one step back. This is a recommendation but there might better ways to go. Good luck! -- Cheers, Felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
hi, I still don’t understand why the relays constantly go offline for no apparent reason С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
I see. Thanks 02.05.2020, 10:38, "teor" :Hi, On 2 May 2020, at 00:07, Станиславwrote: 01.05.2020, 14:20, "teor" :Hi, On 1 May 2020, at 20:57, Станислав wrote: what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end line May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated stringWhere is it happening?Client or relay?Can you share a few more log lines?If it's a relay, maybe your connection just got cut off.Looks like a relay, and relays use unencrypted DIrPorts for directory downloads. So maybe:* the connection got cut off* the remote relay is sending corrupted data* the data was modified in transit There's nothing you need to do. T,___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] (no subject)
Hi, > On 2 May 2020, at 00:07, Станислав wrote: > > 01.05.2020, 14:20, "teor" : > Hi, > > > On 1 May 2020, at 20:57, Станислав wrote: > > what could it mean > > May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end > line > May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or > generated string > > Where is it happening? > Client or relay? > > Can you share a few more log lines? > > If it's a relay, maybe your connection just got cut off. > Looks like a relay, and relays use unencrypted DIrPorts for directory downloads. So maybe: * the connection got cut off * the remote relay is sending corrupted data * the data was modified in transit There's nothing you need to do. T___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
01.05.2020, 14:20, "teor" :Hi, On 1 May 2020, at 20:57, Станиславwrote: what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end line May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated stringWhere is it happening?Client or relay?Can you share a few more log lines?If it's a relay, maybe your connection just got cut off.T ,___tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relaysMay 01 13:40:13.000 [notice] Tor 0.4.2.7 opening new log file.May 01 13:40:13.986 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.May 01 13:40:13.987 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warningMay 01 13:40:13.987 [notice] Read configuration file "/etc/tor/torrc".May 01 13:40:13.993 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.May 01 13:40:13.993 [notice] Based on detected system memory, MaxMemInQueues is set to 2947 MB. You can override this by setting MaxMemInQueues by hand.May 01 13:40:13.993 [warn] MyFamily is set but ContactInfo is not configured. ContactInfo should always be set when MyFamily option is too.May 01 13:40:13.995 [notice] Opening OR listener on 0.0.0.0:443May 01 13:40:13.995 [notice] Opened OR listener on 0.0.0.0:443May 01 13:40:13.995 [notice] Opening OR listener on [2a03:e2c0:bc7::2]:443May 01 13:40:13.995 [notice] Opened OR listener on [2a03:e2c0:bc7::2]:443May 01 13:40:13.995 [notice] Opening Directory listener on 0.0.0.0:80May 01 13:40:13.995 [notice] Opened Directory listener on 0.0.0.0:80May 01 13:40:14.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.May 01 13:40:14.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.May 01 13:40:15.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.May 01 13:40:15.000 [notice] Your Tor server's identity key fingerprint is 'armik CE5ED345398CC02D573347C2F238F80B18E680EE'May 01 13:40:15.000 [notice] Bootstrapped 0% (starting): StartingMay 01 13:40:15.000 [notice] Starting with guard context "default"May 01 13:40:17.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.May 01 13:40:18.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.May 01 13:41:40.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.May 01 13:41:40.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6796, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)May 01 13:41:43.000 [notice] Bootstrapped 5% (conn): Connecting to a relayMay 01 13:41:43.000 [notice] Bootstrapped 10% (conn_done): Connected to a relayMay 01 13:41:43.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relayMay 01 13:41:43.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay doneMay 01 13:41:43.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptorsMay 01 13:41:44.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.May 01 13:41:48.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptorsMay 01 13:41:50.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptorsMay 01 13:41:51.000 [notice] Bootstrapped 65% (loading_descriptors): Loading relay descriptorsMay 01 13:41:52.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptorsMay 01 13:41:52.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuitMay 01 13:41:54.000 [notice] Bootstrapped 100% (done): DoneMay 01 13:41:54.000 [notice] Now checking whether ORPort 178.140.230.147:443 and DirPort 178.140.230.147:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)May 01 13:41:54.000 [notice] Self-testi
Re: [tor-relays] (no subject)
Hi, > On 1 May 2020, at 20:57, Станислав wrote: > > what could it mean > > May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end > line > May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or > generated string Where is it happening? Client or relay? Can you share a few more log lines? If it's a relay, maybe your connection just got cut off. T signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end lineMay 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated string С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
now.on one relay once a day constantly loads a new descriptor. CE5ED345398CC02D573347C2F238F80B18E680EE С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On Fri, Mar 22, 2019 at 10:17:26PM +0200, Ahmed Ahmed wrote: > [empty message] I just set the 'moderated' bit on this person, so further messages (after these two) will need manual attention before they make it to the list. Hopefully that will keep the signal-to-noise ratio on the right side of the line. :) Sorry for the troubles, --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
aboske...@gmail.com ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Envoyé de mon iPhone ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
1___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
What assistance do you need? - Original Message - From: "Laty Luck" To: tor-relays@lists.torproject.org Sent: Wednesday, October 11, 2017 11:33:52 PM Subject: [tor-relays] (no subject) help ___ 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] (no subject)
help ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Also, unsubscription requests require you to confirm the request, so you can't unsubscribe someone else by entering their address. On Wed, Mar 29, 2017, at 00:34, Dave Warren wrote: > Why not unsubscribe yourself? You figured out how to subscribe, you > can figure out how to unsubscribe. > > The first step is to click the link in the footer of every single > message, then look for "To unsubscribe from tor-relays" > > On Wed, Mar 29, 2017, at 00:31, Nicholas K S Cullen wrote: >> Please.unsubscribe me >> _ >> 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] (no subject)
Why not unsubscribe yourself? You figured out how to subscribe, you can figure out how to unsubscribe. The first step is to click the link in the footer of every single message, then look for "To unsubscribe from tor-relays" On Wed, Mar 29, 2017, at 00:31, Nicholas K S Cullen wrote: > Please.unsubscribe me > _ > 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] (no subject)
Please.unsubscribe me ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Please unsubscribe me ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
mario ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Bridges can be gotten over email, also, at brid...@bridges.torproject.org with "get bridges" in the body. On 29 November 2016 at 19:36, fnordomat wrote: > you can get them from https://bridges.torproject.org > > dark side: > > i need some relays bridges to use > > ___ > ___ > 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] (no subject)
you can get them from https://bridges.torproject.org dark side: > i need some relays bridges to use > ___ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
i need some relays bridges to use ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Hi On Jun 10, 2016 11:17 AM, "JOHNY CAMPOS" wrote: > > > ___ > 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] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
2015/11/8 10:51:15.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:51:15.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:51:15.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:51:43.300 [WARN] Error parsing Bridge address 'cert=MIST1psNVCb8KwXFb7UK7qO+HgnDF7C72lXxDeVOPEJVYDl2c6OuWgW26uZ8b2qeOOFaTg' 2015/11/8 10:51:43.300 [WARN] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details. 2015/11/8 10:52:54.300 [WARN] Error parsing Bridge address 'cert=MIST1psNVCb8KwXFb7UK7qO+HgnDF7C72lXxDeVOPEJVYDl2c6OuWgW26uZ8b2qeOOFaTg' 2015/11/8 10:52:54.300 [WARN] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details. 2015/11/8 10:53:21.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:53:21.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:53:21.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:53:21.300 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:53:28.000 [NOTICE] Bootstrapped 5%: Connecting to directory server 2015/11/8 10:53:28.000 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 2015/11/8 10:53:28.000 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 10:53:28.000 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:53:28.000 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:55:47.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:55:47.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:55:47.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:56:12.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:12.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:12.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:12.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:56:18.900 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 10:56:18.900 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:56:18.900 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:56:38.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:56:38.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:38.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:56:38.400 [NOTICE] Ignoring directory request, since no bridge nodes are available yet. 2015/11/8 10:56:38.900 [NOTICE] Delaying directory fetches: DisableNetwork is set. 2015/11/8 10:56:52.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:52.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:52.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:52.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:56:58.900 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:56:58.900 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 10:56:59.000 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:57:57.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:57:57.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:57:57.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:58:05.000 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:58:11
[tor-relays] (no subject)
obfs3 192.36.27.98:46121 0DEFB4F0212B8926D2F9B50E1A4149DC3F00CDC6 obfs3 194.68.32.238:44551 3C58A260CB4C5259B0214E63F384CD958934816C obfs3 54.201.127.175:40872 3DB93D8D4E1C02BA1FB6C881C18433091712A544 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
8e10f0be03478ac378eb8562bd71e3757734fd75 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Don’t threads like this belong on tor-talk? > On 8 Oct 2015, at 08:44, Kenneth Freeman wrote: > > It's our version of 4'33". > > On 10/07/2015 09:00 AM, Dominik Ungar wrote: >> Was this thread created by accident? >> Am 07.10.2015 13:56 schrieb "Bandie Yip Kojote" : >> >> I guess you are right. >> >> On 10/07/2015 01:48 PM, ??? wrote: > > > ___ tor-relays mailing > list tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > <0xDD79757F.asc>___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F signature.asc Description: Message signed with OpenPGP using GPGMail ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
It's our version of 4'33". On 10/07/2015 09:00 AM, Dominik Ungar wrote: > Was this thread created by accident? > Am 07.10.2015 13:56 schrieb "Bandie Yip Kojote" : > > I guess you are right. > > On 10/07/2015 01:48 PM, ??? wrote: ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays 0xDD79757F.asc Description: application/pgp-keys 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] (no subject)
Was this thread created by accident? Am 07.10.2015 13:56 schrieb "Bandie Yip Kojote" : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > I guess you are right. > > On 10/07/2015 01:48 PM, ??? wrote: > > > > > > ___ 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 > > iL4EAREKAGYFAlYVBrpfFIAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl > bnBncC5maWZ0aGhvcnNlbWFuLm5ldDFFMTBDQzEyNzY0RTlBMjc4RTAzMzhDMEQ4 > ODhGQjg0MDYwN0UwOTQACgkQ2Ij7hAYH4JRSAAD+MhdUBPLQ2L1yayT9KZKFcKu1 > I1vodMy3gTXqXL2+sIoA/30T3merghOc7YKhRhGzhCA+0jvq7+bfu6Z9Y91m3vwx > =ZguS > -END PGP SIGNATURE- > ___ > 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] (no subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I guess you are right. On 10/07/2015 01:48 PM, ??? wrote: > > > ___ 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 iL4EAREKAGYFAlYVBrpfFIAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDFFMTBDQzEyNzY0RTlBMjc4RTAzMzhDMEQ4 ODhGQjg0MDYwN0UwOTQACgkQ2Ij7hAYH4JRSAAD+MhdUBPLQ2L1yayT9KZKFcKu1 I1vodMy3gTXqXL2+sIoA/30T3merghOc7YKhRhGzhCA+0jvq7+bfu6Z9Y91m3vwx =ZguS -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Re ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Hi! Welcome to the club! Doing some quick math based your avg speed and your total transfer, it looks like you've been running an exit relay for about a day. It takes some time to build consensus within the network, others can explain it better and in more detail.Don't worry, it takes some time for the network to give you much love, but it will! Take a look at one of my newest relays on atlas to see the ramp-up time. It's only been up for a couple of days. https://atlas.torproject.org/#details/E0FE2E053843F09480EFF75F0A27D095F96FFF82 Here's an another relay, that shows once love starts, it stays. This one has been up for over a month... One of my first. https://atlas.torproject.org/#details/BDE26705D49CB8AC3297953BCC2070FED9C61153 Don't forget to provide the fingerprint for others to investigate. :) Matt -- Speak Freely ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Hi, I have these settings in my torrc-file RelayBandwidthRate 1 KB # Throttle traffic to >1000KB/s (800Kbps) RelayBandwidthBurst 2 KB # But allow bursts up >to 2000KB/s (1600Kbps) MaxAdvertisedBandwidth 1 KB I have a decent cable-based internet-connection at >home and want to share lots of bandwith. > Unfortunately my exit node only does about 220kb/sec >avg: 219.2 Kb/sec, total: 18.4 GB avg: 224.7 Kb/>sec, total: 18.5 GB > What do i have to change to speed this up? Thank you for running a Relay. Please provide your fingerprint if you want other people to look into this matter. -- Sincerely yours / Sincères salutations / M.f.G. Sebastian Urbach - Religion is fundamentally opposed to everything I hold in veneration - courage, clear thinking, honesty, fairness, and, above all, love of the truth. - Henry Louis Mencken (1880 - 1956), American journalist, essayist, magazine editor, satirist and critic. On February 20, 2015 1:36:43 PM "Volker Mink" wrote: ___ 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] (no subject)
Hello. I have these settings in my torrc-file RelayBandwidthRate 1 KB # Throttle traffic to 1000KB/s (800Kbps) RelayBandwidthBurst 2 KB # But allow bursts up to 2000KB/s (1600Kbps) MaxAdvertisedBandwidth 1 KB I have a decent cable-based internet-connection at home and want to share lots of bandwith. Unfortunately my exit node only does about 220kb/sec avg: 219.2 Kb/sec, total: 18.4 GB avg: 224.7 Kb/sec, total: 18.5 GB What do i have to change to speed this up? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Hej, Reportedly Pirate Bay runs virtual machines in someone else's clouds dodging revealing their IPs because traffic is handled by a load balancer. Why couldn't Tor be run in China, for example, using that method as there are cloud companies there? Robert ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
It looks like VPS/Debian says differently. It was solved by installing sudo which I would not have guessed was the problem. One thing which is curious and a problem for Linux ab initios is the VPS operating system installations can be irregular and may not have all the bits even on several otherwise identical VPSs. Robert ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 5/6/2014 21:35, I wrote: > Help please getting past this? > > root@a cheap vps:~# gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | > sudo > apt-key add - > -bash: sudo: command not found > gpg: [stdout]: write error: Broken pipe > gpg: build_packet(2) failed: file write error > gpg: WARNING: nothing exported > gpg: key export failed: file write error > > Robert Install sudo. -- staticsafe https://asininetech.com ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
You're already root, you don't need the "sudo" part. On Tue, May 6, 2014 at 9:35 PM, I wrote: > Help please getting past this? > > root@a cheap vps:~# gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | > sudo apt-key add - > -bash: sudo: command not found > gpg: [stdout]: write error: Broken pipe > gpg: build_packet(2) failed: file write error > gpg: WARNING: nothing exported > gpg: key export failed: file write error > > Robert > > ___ > 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] (no subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://lmgtfy.com/?q=write+error%3A+Broken+pipe On Tue, May 06, 2014 at 05:35:32PM -0800, I wrote: > > > content="INBOX.COM" name=GENERATOR> > > Help please getting past this?root@a cheap vps:~# gpg --export > A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add --bash: sudo: > command not foundgpg: [stdout]: write error: Broken pipegpg: > build_packet(2) failed: file write errorgpg: WARNING: nothing > exportedgpg: key export failed: file write errorRobert > > > > > > ___ > 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.14 (GNU/Linux) iQEcBAEBAgAGBQJTaZSOAAoJEAXQWoW8lug/xuAH/0NgBfVdq9TYIiFQgrv2/bbl n+0+kqURWhRuuogjQ47YsCjCIE+wj/pASwBH7e0tao/dA8gRTDCXdi68E69kfZD7 lh5eAHPVBcbmva7+KiwKztQSUtSEqu2X3UVsyPGvIvBHAqd/4S6bt2d69kDA7V5I QLyoDjb4S3/+gHp8pvLNAJrROpfkf0jAn5ogCecLVtle5xAuVo2YkfP/PT4W+iIU rluN1mraniq/Q+TB4pMg3RMWuV2Lxq8kCugmfHA+sylUbiVYXMoVRDb5QP92sdgX aZJrChAmbU5ikAQ1ItXmhlXpoAmaDIouc//RazEodeSmzCkvtZOhU6hL0xY5v5k= =WNLq -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Help please getting past this?root@a cheap vps:~# gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add --bash: sudo: command not foundgpg: [stdout]: write error: Broken pipegpg: build_packet(2) failed: file write errorgpg: WARNING: nothing exportedgpg: key export failed: file write errorRobert ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Hello Hey since the open ssl was found you folks have been pounding my e-mail box I understand ,anyway can't authenticate my password to unsubscribe for a bit could you send it to my e-mail I have updated my yahoo e-mail password like they said. Sincerely John P. Katakowski.___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
howdy i am interested in helping updating and patching the tor code van one of the developers contact me off list or some of you i am interested ih helping updating all parts of tor and any project of tor -- the wyer ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 2/25/14, Roger Dingledine wrote: > On Tue, Feb 25, 2014 at 02:27:22PM +1100, Zenaan Harkness wrote: >> tor >> should never stop running (or crash) with just a config file reload! > > Alas, I disagree. The alternative is that it *doesn't* stop running, > yet you think it's using the new torrc file when it isn't. That would > be a worse kind of surprise. > > Unless you have a third alternative that is better? I agree that the > current state is not great. > > That said, we *do* have a partial answer, in the init script itself -- it > runs Tor with --verify-config to make sure that the config file itself is > parseable. So the remaining trouble is when the config file is parseable, > but the requested changes are incompatible with Tor's current state. Aha. Thank you. What would be preferable from my personal POV is that an attempt to load the config file would fail with an error output to the console. In debian, there are six standard options for service management: status start stop reload restart force-reload reload ought not cause the daemon to stop. Sometimes daemons have restart and force-reload be the same thing. force-reload is where the daemon might be restarted if there is a config file change which cannot be effected otherwise. At least, that's my understanding, although I'm not an expert sorry. >> DisableDebuggerAttachment 0 >> >> This is the only change, the one which subsequent to adding that >> option, and running service tor reload, tor apparently stopped >> running, as above. > > Yes. Please read your Tor logs where it explains why. > > https://www.torproject.org/docs/faq#Logs > >> So the only change that I am aware of that could have caused the HSDir >> flag (as shown in arm) to go away, was either that option >> (DisableDebuggerAttachment 0), or simply the fact that the relay >> crashed (or somehow otherwise stopped running). > > It's the latter -- the HSDir flag is a function of the stability of your > relay. See > https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt#l1867 Thank you for the pointers and clarity. Very much appreciated. Zenaan ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On Tue, Feb 25, 2014 at 02:27:22PM +1100, Zenaan Harkness wrote: > tor > should never stop running (or crash) with just a config file reload! Alas, I disagree. The alternative is that it *doesn't* stop running, yet you think it's using the new torrc file when it isn't. That would be a worse kind of surprise. Unless you have a third alternative that is better? I agree that the current state is not great. That said, we *do* have a partial answer, in the init script itself -- it runs Tor with --verify-config to make sure that the config file itself is parseable. So the remaining trouble is when the config file is parseable, but the requested changes are incompatible with Tor's current state. > DisableDebuggerAttachment 0 > > This is the only change, the one which subsequent to adding that > option, and running service tor reload, tor apparently stopped > running, as above. Yes. Please read your Tor logs where it explains why. https://www.torproject.org/docs/faq#Logs > So the only change that I am aware of that could have caused the HSDir > flag (as shown in arm) to go away, was either that option > (DisableDebuggerAttachment 0), or simply the fact that the relay > crashed (or somehow otherwise stopped running). It's the latter -- the HSDir flag is a function of the stability of your relay. See https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt#l1867 --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 2/25/14, Roger Dingledine wrote: > On Tue, Feb 25, 2014 at 10:15:11AM +1100, Zenaan Harkness wrote: >> I'm on Debian and did a service tor reload (not restart) and tor >> crashed! I didn't realise immediately, took may be a minute to realise >> and restart. Anyway apologies to any connections that were going >> through this relay. >> >> Should I report a bug to Debian? > > First check your logs -- it's likely that it's not a crash, but rather > Tor read the new torrc file and either couldn't parse it or refused to > switch to the new parameters. I ran service tor status, and it was definitely dead. What twigged me was rerunning arm and arm began with running some wizard for "new site" configuration, so I knew something had gone wrong, checked the service and sure enough it was "not running". service tor start and all was back and running within a minute or less, and arm showed me as much. So definitely tor stopped running - in a way that was deterministic (I did run the service tor reload command) but totally unexpected - tor should never stop running (or crash) with just a config file reload! >> Also, this morning, my relay is back up, but no longer with HSDir >> flag. Is this due to setting that option in the torrc file? And if so, >> I guess it is recommended to disable that option? > > To disable which option? You should leave HidServDirectoryV2 alone in > general, and let the Tor directory authorities decide whether you're > stable enough to be used. DisableDebuggerAttachment 0 This is the only change, the one which subsequent to adding that option, and running service tor reload, tor apparently stopped running, as above. So the only change that I am aware of that could have caused the HSDir flag (as shown in arm) to go away, was either that option (DisableDebuggerAttachment 0), or simply the fact that the relay crashed (or somehow otherwise stopped running). I am very new to running a relay and still getting up to speed - I imagine I will be for a while yet, so thanks everyone for your patience :) Regards Zenaan ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On Tue, Feb 25, 2014 at 10:15:11AM +1100, Zenaan Harkness wrote: > I'm on Debian and did a service tor reload (not restart) and tor > crashed! I didn't realise immediately, took may be a minute to realise > and restart. Anyway apologies to any connections that were going > through this relay. > > Should I report a bug to Debian? First check your logs -- it's likely that it's not a crash, but rather Tor read the new torrc file and either couldn't parse it or refused to switch to the new parameters. > Also, this morning, my relay is back up, but no longer with HSDir > flag. Is this due to setting that option in the torrc file? And if so, > I guess it is recommended to disable that option? To disable which option? You should leave HidServDirectoryV2 alone in general, and let the Tor directory authorities decide whether you're stable enough to be used. --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 2/24/14, Jeroen Massar wrote: > On 2014-02-24 09:32 , Zenaan Harkness wrote: >> I saw a hint of some interesting output by arm: >> flags: Exit, HSDir, Running, V2Dir, ValidleDebuggerAttachment 0' to >> your torrc and restarting tor. For more information see... >> >> This bit "leDebuggerAttachment 0' to your torrc and restarting tor. >> For more information see..." disappeared pretty quick. > > arm needs a few more details from Tor than it can easily get, > effectively it wants to ptrace the Tor process to collect these details. > Hence you'll need to set in torrc: > DisableDebuggerAttachment 0 > That will allow it to collect these details. > See also the description for that option in: > https://www.torproject.org/docs/tor-manual.html.en Thank you. The man page (or something) said that tor would not be able to apply that option whilst running. Nevertheless I added the option into torrc so that next time tor gets restarted, I shall be able to use arm properly. I'm on Debian and did a service tor reload (not restart) and tor crashed! I didn't realise immediately, took may be a minute to realise and restart. Anyway apologies to any connections that were going through this relay. Should I report a bug to Debian? Also, this morning, my relay is back up, but no longer with HSDir flag. Is this due to setting that option in the torrc file? And if so, I guess it is recommended to disable that option? PS Apologies for forgetting the subject line. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 2014-02-24 09:32 , Zenaan Harkness wrote: > I saw a hint of some interesting output by arm: > > flags: Exit, HSDir, Running, V2Dir, ValidleDebuggerAttachment 0' to > your torrc and restarting tor. For more information see... > > This bit "leDebuggerAttachment 0' to your torrc and restarting tor. > For more information see..." disappeared pretty quick. arm needs a few more details from Tor than it can easily get, effectively it wants to ptrace the Tor process to collect these details. Hence you'll need to set in torrc: DisableDebuggerAttachment 0 That will allow it to collect these details. See also the description for that option in: https://www.torproject.org/docs/tor-manual.html.en Greets, Jeroen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
I saw a hint of some interesting output by arm: flags: Exit, HSDir, Running, V2Dir, ValidleDebuggerAttachment 0' to your torrc and restarting tor. For more information see... This bit "leDebuggerAttachment 0' to your torrc and restarting tor. For more information see..." disappeared pretty quick. Any ideas what that would be? TIA Zenaan ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Fabiano, You're aware this is a public mailing list, where everything posted here is already public right, and any police force who want to can already see it? And you're also aware that while you're subscribed to the mailing list, you will receive everything in said list? You can't tell the entire list to shut up because you don't want to receive them anymore, what you can do is unsubscribe by going here: 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] (no subject)
Please! I am not participate in this forum anymore! Any e mail that coming after this will be reported to Uk intelligence police (M15) Be aware pls with all posts or e mails here ! Have a nice weekend to all > On 14 Jan 2014, at 20:28, Jeroen Massar wrote: > >> On 2014-01-14 21:05, I wrote: >> Jeroen, >> >> Thank you. It did that but I can't see a change. > > NTP adjusts slowly, as your clock is 6+ hours off, you should force the > timesync first, eg with with rdate (apt-get install rdate): > > rdate -v ntp.xs4all.nl > > should do the trick. Then after that make sure that ntpd is running: > /etc/init.d/ntp restart > >> The VPS person said it is set to UTC. Previously on another VPS it >> was another relay in the ?circuit which had the time difference. > > UTC is a timezone, and having that is great as it avoids all the > pitfalls and annoyances with summer/winter time. > > Note that some VPSs do not allow changing of the time, one will have to > ask the host to set the time. > > Do note that a VPS can be inspected and controlled easily by the Host, > as such, make sure that you trust that operator. > > Greets, > Jeroen > > > ___ > 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] (no subject)
On 2014-01-14 21:05, I wrote: > Jeroen, > > Thank you. It did that but I can't see a change. NTP adjusts slowly, as your clock is 6+ hours off, you should force the timesync first, eg with with rdate (apt-get install rdate): rdate -v ntp.xs4all.nl should do the trick. Then after that make sure that ntpd is running: /etc/init.d/ntp restart > The VPS person said it is set to UTC. Previously on another VPS it > was another relay in the ?circuit which had the time difference. UTC is a timezone, and having that is great as it avoids all the pitfalls and annoyances with summer/winter time. Note that some VPSs do not allow changing of the time, one will have to ask the host to set the time. Do note that a VPS can be inspected and controlled easily by the Host, as such, make sure that you trust that operator. Greets, Jeroen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Jeroen, Thank you. It did that but I can't see a change. The VPS person said it is set to UTC. Previously on another VPS it was another relay in the ?circuit which had the time difference. Now I see this:- Our clock is 6 hours, 25 minutes behind the time published in the consensus network status document (2014-01-14 19:00:00 UTC). Tor needs an accurate clock... Jan 14 07:34:57.000 [notice] Bootstrapped 5%: Connecting to directory server. Jan 14 07:34:57.000 [notice] Bootstrapped 10%: Finishing handshake with directory server. Jan 14 07:34:57.000 [notice] We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make y$ Jan 14 07:34:57.000 [notice] To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features. Jan 14 07:34:57.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection. Jan 14 07:34:58.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus. Jan 14 07:34:58.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor. Jan 14 07:34:58.000 [notice] Bootstrapped 50%: Loading relay descriptors. Jan 14 07:37:11.000 [notice] New control connection opened. whereat it stays. Any ideas, please. Robert >> Does anyone know how to get past this to get the exit running on Debian >> 6, please? >> >> Our clock is 6 hours, 48 minutes behind the time published in the >> consensus network status document (2014-01-14 11:00:00 UTC). > > apt-get install ntp > > would be a good start. > > Greets, > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 2014-01-14 12:38, I wrote: > Does anyone know how to get past this to get the exit running on Debian > 6, please? > > Our clock is 6 hours, 48 minutes behind the time published in the > consensus network status document (2014-01-14 11:00:00 UTC). apt-get install ntp would be a good start. Greets, Jeroen ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
* I schrieb am 2014-01-14 um 12:38 Uhr: > Our clock is 6 hours, 48 minutes behind the time published in the > consensus network status document (2014-01-14 11:00:00 UTC). Tor needs > Does anyone know how to get past this to get the exit running on Debian 6, > please? Do you use a VPS? You basically have to ask them to set the correct time. Or you have to set the time manually. -- Jens Kubieziel http://www.kubieziel.de Das Elend dieser Welt abzubilden ist nicht genug. Man muß sich auch bemühen, einen Ausweg zu finden. Friedrich Gulda signature.asc Description: Digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Does anyone know how to get past this to get the exit running on Debian 6, please? Our clock is 6 hours, 48 minutes behind the time published in the consensus network status document (2014-01-14 11:00:00 UTC). Tor needs an$Jan 13 23:11:25.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.Jan 13 23:17:09.000 [warn] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Connection timed out; TIMEOUT; count 10; recommendation warn)Jan 13 23:17:09.000 [warn] 9 connections have failed:Jan 13 23:17:09.000 [warn] 6 connections died in state connect()ing with SSL state (No SSL object)Jan 13 23:17:09.000 [warn] 3 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKEJan 13 23:23:22.000 [notice] New control connection opened.Robert ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Atlas was accurate but Torstatus has the contact details wrong for mine. > Since i switched to 0.2.4.19 a few days ago i noticed some strange > behaviour. Sometimes the data seems to he corrupted i see on > torstatus.info. The atlas data seems to be right though. Afaik only the > contact and family data seems to be wrong. > > https://atlas.torproject.org/#details/3C82285FAC2171FA5178340A82B05F2190AB68E9 > > http://torstatus.info/router_detail.php?FP=3c82285fac2171fa5178340a82b05f2190ab68e9 > --- > Religion is a symptom of irrational > belief and groundless hope. > --- FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Hi, Am 2013-12-25 20:55, schrieb Sebastian Urbach: > Since i switched to 0.2.4.19 a few days ago i noticed some strange behaviour. > Sometimes the data seems to he corrupted i see on torstatus.info. The atlas > data seems to be right though. Afaik only the contact and family data seems > to be wrong. > > https://atlas.torproject.org/#details/3C82285FAC2171FA5178340A82B05F2190AB68E9 > > http://torstatus.info/router_detail.php?FP=3c82285fac2171fa5178340a82b05f2190ab68e9 > > Im not sure what to make of it right now. A bitcoin for your thoughts ... This is a bug in the old TorStatus software. The update script periodically obtains its data from the Tor process and gets confused by the strings "onion-key" and "ntor-onion-key". This is something that needs to be fixed by the operator of the respective TorStatus page. Fot instance, the TorStatus page at torstatus.blutmagie.de and mine at torstatus.rueckgr.at get it right: http://torstatus.blutmagie.de/router_detail.php?FP=3c82285fac2171fa5178340a82b05f2190ab68e9 http://torstatus.rueckgr.at/router_detail.php?FP=3c82285fac2171fa5178340a82b05f2190ab68e9 In my TorStatus installation, I fixed that problem by replacing if ($line =~ /onion-key/) by if ($line =~ /onion-key/ && $line !~ /ntor-onion-key/) in tns_update.pl. Regards, Paul ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Dear Colleagues, Since i switched to 0.2.4.19 a few days ago i noticed some strange behaviour. Sometimes the data seems to he corrupted i see on torstatus.info. The atlas data seems to be right though. Afaik only the contact and family data seems to be wrong. https://atlas.torproject.org/#details/3C82285FAC2171FA5178340A82B05F2190AB68E9 http://torstatus.info/router_detail.php?FP=3c82285fac2171fa5178340a82b05f2190ab68e9 Im not sure what to make of it right now. A bitcoin for your thoughts ... -- Mit freundlichen Grüssen / Sincerely yours Sebastian Urbach --- Religion is a symptom of irrational belief and groundless hope. --- Gregory House, M.D. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
00:11][BlakbirdzejA] ()+_earth changes spawning chaos releases, react to time speeding, and proclaim a more established eternia for all exisT. aviod control, imperge immortality and fight with new designs without permitting harm, devour opposites, refrain from weakness hiding in false powers. when the weather shifts 2 death burn the corpses and re-taliate with health and completionZ, do not starve there is soil and water for all to eat for 100s of years. gather and destroy not-wanted pain and looping, seperate for strength and evolve. SeX interRaciaLL to merge galaxy code N eradicate idolismz BBZzXArmy8::22 }{}{}{}{}{}{}{}{ BbZzXArmy PrajectoRkiDD MASS CHAIN MESSAGE read and spread to all your friendlists (. http://zeja11.blogspot.com/ .) 22eterniA .xex___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 13-11-08 12:04 AM, bbzxrmy wowman wrote: > > high, i recently set my relay and also mailing list, however my screen > name "BBZzXArmy does not show on the tor world map, can anyone confirm > or help me with this im pissed at it According to the Tor Directory Protocol v3 (search for "named") Newer Naming authorities run a script that registers routers in their mapping files once the routers have been online at least two weeks, no other router has that nickname, and no other router has wanted the nickname for a month. If a router has not been online for six months, the router is removed. https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=dir-spec.txt ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Hi! On Thu, 2013-11-07 at 21:04 -0800, bbzxrmy wowman wrote: > high, i recently set my relay and also mailing list, however my screen name > "BBZzXArmy does not show on the tor world map, can anyone confirm or help me > with this im pissed at it Can you tell us more details about your relay? - Which version of tor do you use on which operating system? - How did you configure it? - The logfile is always a good location to check if the relay is running without problems. So it might help us to help you if you provide details. Some messages you should see are: Sep 18 13:15:46.000 [notice] Your Tor server's identity key fingerprint is 'idkneitzel A17238CF4E82EBD74414F78C313FBA9A157874A3' Sep 18 13:15:48.000 [notice] We now have enough directory information to build circuits. Sep 18 13:15:53.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. With kind regards, Konrad -- Konrad Neitzel signature.asc Description: This is a digitally signed message part ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
high, i recently set my relay and also mailing list, however my screen name "BBZzXArmy does not show on the tor world map, can anyone confirm or help me with this im pissed at it zigzagarmy }{}{}{}{}{}{}{}{ BbZzXArmy PrajectoRkiDD MASS CHAIN MESSAGE read and spread to all your friendlists (. http://zeja11.blogspot.com/ .) 22eterniA .xex___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Uhhh, wut? On 27/09/2013 14:23, ابوصالح wrote: > > Android > > مرسل من الهاتف المحمول Samsung > > > ___ 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] (no subject)
Android مرسل من الهاتف المحمول Samsung___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Uhh, what? This is a mailing list. You signed up to it, and you will need to remove yourself by signing into here: 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] (no subject)
Hello, Can you remove my email adress from your contact list? Thanks in advance. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
Andreas I've tried to contact you a number of times in the past few months. I'm in the process of starting a torservers.net entity here in Iceland for the express purpose of hosting fast exits. I'd like to know how much it will cost to colocate an exit at Datacell. -kupo ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Sent from Samsung Mobile___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On Tue, Sep 27, 2011 at 06:25:49PM +, Tim Myers wrote: > Stop Can't stop the signal. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
On 27/09/2011 19:25, Tim Myers wrote: Stop Sent via BlackBerry by AT&T ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Go ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
Stop Sent via BlackBerry by AT&T ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays