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: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTML HEADMETA http-equiv=Content-Type content=text/html; charset=utf-8META content=INBOX.COM name=GENERATOR/HEAD BODY Help please getting past this?brbrroot@a cheap vps:~# gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -br-bash: sudo: command not foundbrgpg: [stdout]: write error: Broken pipebrgpg: build_packet(2) failed: file write errorbrgpg: WARNING: nothing exportedbrgpg: key export failed: file write errorbrbrRobertbr /BODY /HTML ___ 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
Re: [tor-relays] Avoiding sinkholes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Mar 28, 2014 at 06:48:21AM +0100, Moritz Bartl wrote: Hi Ramo, Thanks for running an exit! Thanks. I've been running one for ages, but the appreciation is always nice. You will run into similar trouble again and again, unfortunately. This is the first time I've known this to happen, I've had this configuration for ... probably 2 years? My suggestion: Get a second IP, or even better, don't share the same VPS. Not sure why a second IP never occurred to me. Good idea. Cheers Damian -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJTNRudAAoJEAXQWoW8lug/hk0H/i+/azfb/CYn31v+UXoYc9NF zMqQUFTeJSiLrXU43QLPb/RLG5XyBWRZNZcoBwdU0x6m4MmoNHg4QpA+HTRWzzUo aQj+ieUcQ1EWm2NZ7Q/ovuYMYyYP38/Y3aUID5sRr0vEYupKNwsztf3VDFjyJziK jsP6BVug0jeBuac5q42t6dk8w4CUUNQRlamvhRFQBMWJJPaMd+MPKNwYcf8eNELO sH96/iTx/kvNBEgueHQyttXa2zcEg3ErhabqdMCSOHIUp7y09T+97Plx6qy9iNL/ eTXf75ZT/57ELzmhrWLXTAdLuGy52yNwwDParI2+w+Q1v61freEobFy5wCA3jZs= =Jjoz -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Tor plugin for Nagios - Alpha release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya List As I mentioned a few weeks ago, I am developing a tor plugin for nagios. Well, today, the first alpha release is out, available at https://github.com/goodvikings/tor_nagios/tree/v0.01 . Currently it supports 6 different checks: 1 - A page fetch through the socks proxy port 2 - Hibernation state 3 - Current bandwidth 4 - OR port reachability 5 - DIR port reachability 6 - Bytes remaining until hibernation If you're interested please give it a go, feedback is more than welcome. Additionally, if you want to see any additional checks implemented, give us a yell. Cheers Ramo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJTH7neAAoJEAXQWoW8lug/ws8H/RxVSKi3Ft8Lr/a3DKi+JMIC HNpOWrGbJEY3RWaJAx/H2L32KC5lE1mJbHm7BI3H1JTmdGkXmkFkyM4pou2/XQg6 DfJO+Zd7LGuJlIzqED3fyH7jB+SA4Syu+eOD710kYF4zQKBmsOy/qqW7R6Ymgq8Q 88JUUuYveAWIDgqir8WwBe8SqJsIWriVd5bObzzB5GZXiZarfMG6dw/kmJicZgyG QUOrddU/9ndrO7B3PCM8JmlB9xHMMuH97up9jS0/kIQFDUiejN/NM62AyDApd+Ef 5jqG8+E6wYWli3mlsc0d3ge4Wix0HPLhllHMxsxrTK3A3quveyVT7pZiO7t1Yas= =awZI -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Tor plugin for Nagios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Heya List I've recently started on developing a nagios plugin for tor, since a cursory google search didn't come up with anything I would describe as 'comprehensive.' Generally speaking, it works by connecting to the control port and running various commands to check the health of the server. You would either drop it on the Tor box and run it with NRPE, or on the monitoring server and open your control port to that IP. So far I've implemented / plan to implement the following checks: * Fetch a page through the socks port * Check if the server is hibernating * Check the current bandwidth (up and down combined) * Check the accounting values (how close to hibernation) * OR / Dir port reachable It's in a very early stage at the moment, but I'm posting here now to ask: Are there any other checks relay operators would want to see implemented? You can check out the code so far at https://github.com/goodvikings/tor_nagios/ Cheers Ramo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJTEsR5AAoJEAXQWoW8lug/m7AH/iEJ6X1kKcOCkUkhgVHyT6aX Nusu9yADtaRzyNrRUtWIgHw80SQSItr8Sgtt9pGIDZssetUYyxKCPN7YFztBJGL5 Fym/Iv+lF6jCyyWRm4SH84yA3k/rW+gPiiNg0mw5di6V2Bx311GM2YavOnZWs0Yh rdX2ljdqbJuIQIOxhaMVrX3jYFRCYv6LvSZwxh9CA8KVgvosiiQTU76ubekoZoCt XUXLepqgD+sUxeRh7QWrM8BxTkY1Yp0XxXaeU87aO40sBB18dozgXuBsTO43ssvK s82iYorusIPdpjuVIr6FnmPrbwuDEaWVJ6ktcVz9Z9WRMP5AbJISU7LuRSxRNBU= =m/S7 -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] schedule tor relay uptime/ bandwidth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I dunno if there's nything built in to tor. Are you on Linux? You coud use cron. Every day at 9 run 'service tor stop', every day at 5 run 'service tor start' Cheers Ramo On Sat, Feb 22, 2014 at 03:51:43PM +1100, Zenaan Harkness wrote: I know tor relay bandwidth usage per period can be configured, but is it possible to schedule a tor relay to sleep during business hours, and only operate after hours? TIA Zenaan ___ 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) iQEcBAEBAgAGBQJTCIL9AAoJEAXQWoW8lug/yboH/2czV9RYyqeyE3CtIJyO7Ccc lT9ysvWeUnFZaOTB8W+VmFpMKRE3TV0gxowatTbXWrAru+bnFRQBHVMhyX0ZWpfy CbIp2Yiu471EequH/1Wumx2Qpp73Vjjs5LTqirN+1Yo0A9LxcH2vz/XFmzq0Nj5m iFE25DUE6uiB09hwTJFY7SfOtwsBdHrWPzjjwxZiHjpqTrDgqm3vIFnt3jAnnFSj IYsw0aswVoyV9jKCgftGP/JpfmYwLOtw87QnSbelKb6ktf8F2dPXUthjKvMWDHkH k2vGYAJugEshcVHhGIfLqHxTf4q0x/P7cDBsfAfixmU3aYBfHqdmjz93naAHIf8= =lep5 -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Amazon abuse report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't think this is the right place for you to try and justify your refusal to pay for content people create. I think most people on this list would prefer you keep political opinions not related to tor off list. Cheers Ramo On Sun, Nov 03, 2013 at 11:50:58PM +0100, Lukas Erlacher wrote: Let me chime in here in regards to torrents to be perhaps not the devil's, but the radical's advocate. I'm sure everyone here will agree that a good case can be made that copyright laws as they stand today are a perversion of, and counter-productive to, their original stated intention of advancement of the arts and sciences, and just as leaking secret information and evidence of wrongdoing is a protest and defense against governments that try to hinder freedom and transparency, so is distributing copyrighted cultural goods a protest and defense against content industries (that are often justifiably compared to criminal organisations (MAFIAA) due to their frequently corrupt and abusive conduct) that attempt to censor culture in order to excise maximum profit from it. Cultural goods that should be preserved and made available to everyone rot away every day because they were not allowed to be preserved and distributed. Do not indict torrents because it's all movies and porn of horrible quality - that is defamation. The hollywood movies and the porn may not have much cultural value, but who is the arbiter of what cultural value is? And even if it was found unanimously that porn does not concern culture (hah!), then for every TB of porn and hollywood shite you block, there are Megabytes of bona fide culture liberated from the shackles of copyright that you throw to the wolves, saying it's just torrents. And doesn't wikileaks use mostly torrents for distributing their releases? When you block torrenting, you're making a decision to censor information and speech based on it being done using a method that is predominantly used for illegitimate, illegal activity; in that case, why not shutter Tor entirely? We all know it's mainly used by fraudsters and other criminals, and right now at this time we know that 80% of Tor clients are zombies from a botnet. Censor torrents because your provider will shut you down if you generate DMCA complaints and CD's; censor them because you truly believe that the torrents are a necessary sacrifice to allow the Tor network to continue to function; don't censor them because they don't contain worthwhile speech that deserves to be protected. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJSdtx3AAoJEAXQWoW8lug/W9cIAKCHPD7TAr+XepFfJHcqX5mc aVn+icB/6m5FZPqiMo1fWbFrJtKjjx5nbF5js+zx5O8ndh0W+7nKjg9P/Wdw6ZRx px090znLhD3zjVY3YEa6HL8RCd2d76DlkxTJ7JpvI51wjLSd8W9EMwk4VDrje6ds ayhA4vxeptfDJ2qZY73DBTw0/3C/puXjmSfjq5yQTClucCbPxNhadPW4po/NB5OO pWR4Dwt6uaaiK8+AeynV/ggWS1TzrQTLpVAMuZghyEyrA/RRdHfWS19pQz8lKNg3 lE+lw4sVfoQfKii3XgwpvCSDkAG6bXjyHnUtQ6NUvmUpdkhdZYqDegDhs0flgvQ= =El4R -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
