Re: [tor-relays] Kitten1 and kitten2 compromised (guard/hs/fallback directory)

2017-05-21 Thread Nagaev Boris
On Sun, May 21, 2017 at 10:37 AM, grarpamp wrote: >> remember that they took the relay because >> a *victim* contacted it, not because they think the "guyz behind the >> software" did. > > Civil sue them for stupid thinking / false arrest confiscation, > loss of service and use, public tarnishment

Re: [tor-relays] Legal Status of Relays Worldwide [was: kittens seized]

2017-05-22 Thread Nagaev Boris
On Sun, May 21, 2017 at 8:47 PM, grarpamp wrote: That's actually why the torservers.net people suggest *not* using disk encryption. Having no barriers makes it much easier for the police to realize that there's nothing useful to them. > >>> This falling over may perhaps not be prefe

Re: [tor-relays] Who is running the two biggest Exits in the network?

2017-05-26 Thread Nagaev Boris
On Fri, May 26, 2017 at 3:26 PM, nusenu wrote: >> Since about mid April there are just two similar Exits making up now about >> 4.5% exit probability together. >> Located in Panama, run in the okservers.net network, AS395978 ,they don’t >> give up any further information about themselves. >> >>

Re: [tor-relays] Who is running the two biggest Exits in the network?

2017-05-27 Thread Nagaev Boris
On Sat, May 27, 2017 at 8:00 PM, Duncan wrote: > Hi Paul, > > Paul: >> >> >> I agree with that part. >> >> But sometimes it helps to look and think things from an extreme point of >> view: >> Let's assume the whole TOR would be anonymous in a way that you cant >> see contacts not even nicknames. W

Re: [tor-relays] ORSN DNS servers vs OpenNic

2017-08-04 Thread Nagaev Boris
On Fri, Aug 4, 2017 at 3:18 PM, niftybunny wrote: > I use: > > nameserver 204.152.184.76 > nameserver 194.150.168.168 > nameserver 213.73.91.35 > nameserver 8.8.8.8 > > works fine. Google as gateway of last resort :) I'd add also 77.88.8.8 (https://dns.yandex.ru) and 80.80.80.80 (http://freenom.w

Re: [tor-relays] keepyourprivcay: Introducing a new 100 mbit/s relay

2017-08-10 Thread Nagaev Boris
Thank you for running the relay! On Thu, Aug 10, 2017 at 4:20 PM, Keepyourprivacy wrote: > Hello fellow operators of tor relays out there! :) > > I'd like to introduce my new relay, it's called keepyourprivacy and hosted > in the Netherlands, at a provider which is known for high uptime and great

Re: [tor-relays] blocking >1 connections per ip address onto Tor DirPort

2017-08-15 Thread Nagaev Boris
On Tue, Aug 15, 2017 at 2:08 PM, Toralf Förster wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I do have the following iptables rule here : > > # Tor > # > dirport=80 > orport=443 > > $IPT -A INPUT -p tcp --destination-port $dirport --match conntrack > --ctstate NEW --ma

Re: [tor-relays] More recent rpm somewhere?

2017-09-17 Thread Nagaev Boris
On Sun, Sep 17, 2017 at 8:22 AM, nusenu wrote: >> I'm running a few relays on CentOS 7 >> As I'm sticking to the ease of rpm distributions, I'm left behind on >> 0.2.9.10 from EPEL >> >> Does anyone know of another rpm repository with a more up to date version ? > > I'm not aware of any updated (t

Re: [tor-relays] Testing Golang relay implementation

2017-10-24 Thread Nagaev Boris
Hey Thanks for doing that! It came many times to my mind. There were efforts on implementing Tor relay in Golang before, by Tom van der Woerdt: https://github.com/tvdw/gotor Have you looked at the project? In his blog post https://tvdw.eu/blog/2015/01/24/implementing-a-tor-relay-from-scratch/ To

Re: [tor-relays] my IP got blocked

2017-11-14 Thread Nagaev Boris
On Tue, Nov 14, 2017 at 2:26 PM, Julien ROBIN wrote: > Hi, > > It's not the first time I hear about Non-Exit IP blocked (but may be some > people here are more familiar with the subject) : I don't really know what > are the most used interfaces/websites from which those administrators are > gettin

Re: [tor-relays] So long and thanks for all the abuse complaints

2017-12-04 Thread Nagaev Boris
On Mon, Dec 4, 2017 at 12:39 PM, teor wrote: > Blocking port 80 isn't safe for users: it doubles the number of exits that > they must use, which doubles their risk of a malicious exit. The risk of using port 443 is much lower than the risk of using port 80, because information passed through 443

Re: [tor-relays] Alternative hoster (Re: DigitalOcean bandwidth billing changes)

2018-04-25 Thread Nagaev Boris
On Wed, Apr 25, 2018 at 4:08 PM, Ralph Seichter wrote: > On 25.04.18 14:50, mick wrote: > >> I think I'm immensely lucky to get the service I do. > > Indeed. I guess DigitalOcean's loss will be Hetzner's gain as far as my > business is concerned. See https://www.hetzner.com/cloud . I already use >

Re: [tor-relays] Is Tor-network protected from using one hop?

2018-06-26 Thread Nagaev Boris
On Tue, Jun 26, 2018 at 5:27 PM, Matt Traudt wrote: > On 6/26/18 10:16, dave levi wrote: >> I'm testing few things in Tor and I noticed that if im changing(from the >> source code) the number of hop's(nodes) to be more then 3 hop's it >> work's fine(slowly, but still working) and if im sting only

Re: [tor-relays] Question regarding ethical torrent blocking

2018-07-15 Thread Nagaev Boris
On Sun, Jul 15, 2018 at 12:23 PM, Conrad Rockenhaus wrote: > Hello, > > I was going to ask someone off-list, but the amount of abuse and DCMA > complaints I have received now have been so much that I have decided that > the best action to take is to set an exit policy. I run a couple of exit > nod