Re: [tor-relays] Exit relay seized by police

2015-11-07 Thread Moritz Bartl 
On 11/06/2015 05:31 PM, Kevin Beranek wrote:
> Is there a better list than this one for doing so?  I can't find a list
> that seems more appropriate
> on https://lists.torproject.org/cgi-bin/mailman/listinfo.  Or do I have
> to email the DirAuths directly?  If so, where do I find the addresses to
> use?

The "official way" is to email bad-rel...@lists.torproject.org :
https://blog.torproject.org/blog/how-report-bad-relays

-- 
Moritz Bartl
https://www.torservers.net/
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] VPS/dedi paid with bitcoin for exit node anyone?

2015-11-07 Thread Billy Humphreys 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
 
I personally use ZappieHost - contact them, use a promo code to get it
down to $2.50 a month. Ask them to set reverse DNS, inform them you're
making a Tor relay and to forward on abuse emails, and I get ~2MB/s with
them. The bandwidth is 100GB/month, but it's $1 extra a month for an
extra 100GB, so maybe add 900GB more storage if you want.
Regards,
Billy

On 07/11/2015 23:14, Monoko Satou wrote:
> Hi thar,
>
> I'm looking for relatively cheap dedicated/VPS servers offers for
> hosting more tor exit nodes that can be paid for using Bitcoin. Minimal
> connection speed I'm interested in is 100mbit. I've seen some offers
> here and there but maybe I'm missing something. I'd like fellow node
> operators to share some insight on the topic.
>
> I find the infos currently available on TOR project wiki etc little bit
> rusty. It'd be ideal to compile an article on the topic, if people can
> share their experiences I'd like to donate my time for this purpose that
> methinks other will find helpful if one wants to host a tor relay pretty
> much anonymously.
>
> I for one can share a positive opinion on hosting with "Baltic Servers",
> an LT based company. I'm running 2 exits and 2 relays there for 31 days
> at the moment without many hassle (you can find 'em by looking for
> 'netdive' on torstatus.blutmagie.de or on Atlas). Current average net
> troughoutput  is rx/tx 274.56 Mbit/s  / 265.90 Mbit/s and the abuse
> e-mails are being forwarded.
>
> Cheers,
> -- Netdiver
>
>
>
> ___
> 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
 
iQIcBAEBCAAGBQJWPouIAAoJECGBE+89M6jO2ncQAKJHjdNzd61r4llvR+yWyLUi
RgnD08z7Sk94xcjv5tsqSYJhPvAewhdAzogs8VOhUtRDCWsBIy2L61TM1+NQn9eG
WM9k6FpIVuJ6y/tHyTR1ghBwYM7BEAfWDcNM1swd2TzgQvWU963ny4BMkLFBLi+p
Mh59N8hry3UiUQHfp+3gDB+C2psKtuq4kPybLdPVlwAAigGF4PYqvukw8zq7ttNQ
HUtki82RwLhc/ACvETSPAwoTXvS5deFXtPSNVMJVBXcPBoltAnMLArN6wz+IQb4L
HcxxdwpY9p57qqaSEc8VxBBc3dwX6ChDjTmZqzM6oqzVvC11IRXOsv/JbkXCRRod
CBh5fSwlA+YF/VCxEleSPKaSrCbSB49HzgVz/9aVmx3EZrZIF8FfwiEOYVXa8La4
ojfvQgZC8aKlxy3aG8V1mjaKcQFi+QZ6kcgoyShAwuF2qweZYAytCodS28aPeXkE
lma7frkkYBiiuQ1G1F0/QZJRMGsl6AXQB2Xqfrv24ymlNxjAblH71D0cbQV27C9X
i1KQIim5x9MLhVni5j0kfDdwS/+OeLChYHlZa35Hd93DnrbKdyuoQtBi6pOAkffo
UPDTemeel9WxDZ50WUa/feqNkJ1VPAbTmAVXLXchWA0PDMoQUv9jXZHvI6CZ39iv
l+q4n39T5Zi3BHRBgBty
=qHZt
-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)

2015-11-07 Thread 海洋 
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)

2015-11-07 Thread 海洋 
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

Re: [tor-relays] VPS/dedi paid with bitcoin for exit node anyone?

2015-11-07 Thread Andrew Deason 
On Sat, 07 Nov 2015 23:14:27 +
Monoko Satou  wrote:

> I'm looking for relatively cheap dedicated/VPS servers offers for
> hosting more tor exit nodes that can be paid for using Bitcoin. Minimal
> connection speed I'm interested in is 100mbit. I've seen some offers
> here and there but maybe I'm missing something. I'd like fellow node
> operators to share some insight on the topic.

flokinet.is advertises itself to be tor-friendly, accepts bitcoin, and
claims that you can signup without providing any detailed contact info.
I didn't pay with bitcoin and I didn't try to hide my identity, but the
options appear to be there.

The exit node 'nibbana' (025B66CEBC070FCB0519D206CF0CF4965C20C96E) is
hosted there. Don't assume that node's bandwidth is the max that they
can provide; iirc it's one of their lower-end VPS options and I haven't
spent time optimizing or anything (and it's new). Their VPSes are
supposed to have 100mbps and the dedicated boxes are listed as 1gbps.

My experience has been fine so far with them.

-- 
Andrew Deason
adea...@dson.org

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays