unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: documentation/behavior unclear of (tor-hidden-service)
Date: Mon, 6 Mar 2017 20:19:02 +0000	[thread overview]
Message-ID: <20170306201902.sadyh4jmt5yuuo7r@abyayala> (raw)
In-Reply-To: <20170306184712.GE2185@jasmine>

On 17-03-06 13:47:12, Leo Famulari wrote:
> On Mon, Mar 06, 2017 at 06:00:30PM +0000, ng0 wrote:
> > from my experience they are not needed for a relay. Okay, they would be
> > useful to increase security and to see how how Chinese government
> > officials and their automated services want to get into your server, but
> > it's not really necessary for the relay.
> 
> Slight nitpick: In my experience with iptables, it's not just Chinese
> officials that want to break in to my servers, but rather a dazzling
> multitude of people from all over the world ;)
> 
My experience with OpenNIC and tor on the server side was that it's
mostly government IPs running lazy standard methods trying to get in
where they won't get in anyway.
Just don't use port 22, rate-limit connections (with OpenNIC this worked
a bit) and the IPs which traced back directly to those red zones in
chinese cities marked as "military/government zones" went away :).

But yeah, with tor they were in company of russia, USA, and other
nations trying to do the same ;D

      reply	other threads:[~2017-03-06 19:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 15:59 documentation/behavior unclear of (tor-hidden-service) ng0
2017-03-04 16:21 ` ng0
2017-03-06 10:13   ` Ludovic Courtès
2017-03-06 12:08     ` ng0
2017-03-06 15:45       ` Ludovic Courtès
2017-03-06 16:19       ` dian_cecht
2017-03-06 18:00         ` ng0
2017-03-06 18:47           ` Leo Famulari
2017-03-06 20:19             ` ng0 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170306201902.sadyh4jmt5yuuo7r@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).