Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread Luther Blissett
On Sat, 2014-04-19 at 07:42 -0700, kbesig wrote: 1. As non-admin: /usr/bin/vidalia (process:540): GConf-WARNING **: Client failed to connect to the D-BUS daemon: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call,

Re: [tor-relays] Onion address or clearnet address

2014-02-07 Thread Luther Blissett
On Fri, 2014-02-07 at 06:26 -0500, Tom Ritter wrote: On 6 February 2014 14:51, Thomas Themel tho...@themel.com wrote: Hi, Luther Blissett (lbliss...@paranoici.org) wrote on 2014-02-06: 1. When you access the clearnet you need dns name resolving which need to be proxyfied to avoid dns

Re: [tor-relays] How to force VPS to update to current release?

2014-01-07 Thread Luther Blissett
For reference: https://www.torproject.org/docs/debian.html.en#ubuntu This page describes the proper method of sync'n your sources.list file with Tor project's repos. -- 010 001 111 signature.asc Description: This is a digitally signed message part

Re: [tor-relays] How to force VPS to update to current release?

2014-01-07 Thread Luther Blissett
On Tue, 2014-01-07 at 13:40 -0800, I wrote: Luther, Following that page's help has allowed me to get mulitple VPSs working for Tor but I am asking what to do when apt-get update or yum update doesn't get the newer version of Tor. How an update can be forced is the question. (The

Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)

2013-11-12 Thread Luther Blissett
On Mon, 2013-11-11 at 19:55 -0500, Jeroen Massar wrote: PS: Try doing a packet sniff on a link with thousands of connections and where your user cannot tell you what source IP they have; next to the fact that they might just be using the wrong destination host... ;) Greets, Jeroen

Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)

2013-11-11 Thread Luther Blissett
On Wed, 2013-11-06 at 14:00 +0100, Jeroen Massar wrote: On 2013-11-06 13:47 , mick wrote: On Wed, 06 Nov 2013 14:00:09 +0200 Lars Noodén lars.noo...@gmail.com allegedly wrote: On 11/06/2013 01:26 PM, mick wrote: I disagree. Dropping all traffic other than that which is explicitly

Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)

2013-11-05 Thread Luther Blissett
On Tue, 2013-11-05 at 09:36 +0100, jj tor wrote: Sorry for the confusión, the exact line in my torrc is Socksport 0, so, SOCKS port is closed. Moreover, I haven't got any exit rule towards port 9050 Even if I block this traffic using iptables, I am very curious about why the server is

Re: [tor-relays] Running more nets than Tor?

2013-10-04 Thread Luther Blissett
On Fri, 2013-10-04 at 04:31 -0400, grarpamp wrote: Anyone also offering up vpngate, i2p, mail mixes, other p2p/networks, etc to the public on their relay platform? ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] Relay security, re: local network

2013-09-25 Thread Luther Blissett
On Wed, 2013-09-25 at 19:10 +0300, Joe wrote: Hi, I'm planning to run a Tor relay on a spare computer at home. Security is a concern, and not only regarding the machine running the relay but also my other computers. Are there any (theoretical or otherwise) known attacks a person can

Re: [tor-relays] Future versions and Vidalia?

2013-09-24 Thread Luther Blissett
On Mon, 2013-09-23 at 13:36 +0300, J.C. wrote: So far I haven't seen any other error messages than something about a failed DNS server, which always corrects itself half a second or so afterwards, stating nameservers are back up. It's running on a 100/10 connection, pushing as much upstream

Re: [tor-relays] Sent open privoxy port warning

2013-09-13 Thread Luther Blissett
On Wed, 2013-09-11 at 12:35 -0700, Aaron Hopkins wrote: I sent the following warning to the listed e-mail address of 14 of the 19 Tor nodes I found that accepted connections on port 8118, some of which bounced. If any of you run or know how to get in touch with the operators of the nodes

Re: [tor-relays] Sent open privoxy port warning

2013-09-13 Thread Luther Blissett
Ow, forgot to say, don't bother with that hex. From what I could get with the help of others, this is just a byte reversed/corrupted log entry. Since the hard drive used to store logs is some years old, I guess this is related to badblocks. On Wed, 2013-09-11 at 12:35 -0700, Aaron Hopkins wrote: