From: ng0 <contact.ng0@cryptolab.net>
To: dian_cecht@zoho.com
Cc: guix-devel@gnu.org
Subject: Re: documentation/behavior unclear of (tor-hidden-service)
Date: Mon, 6 Mar 2017 18:00:30 +0000 [thread overview]
Message-ID: <20170306180030.ginyp6tywg2jcpps@abyayala> (raw)
In-Reply-To: <20170306081900.4802e21b@khaalida>
On 17-03-06 08:19:00, dian_cecht@zoho.com wrote:
> On Mon, 6 Mar 2017 12:08:20 +0000
> ng0 <contact.ng0@cryptolab.net> wrote:>
> > Maybe someone else can try and implement this, I only know what'S
> > needed for running the relay but can't do it at the moment ;)
>
> Just for reference sake:
> https://www.torproject.org/docs/tor-doc-relay.html.en
>
> What is the policy on creating/modifying firewalls? Would any relay
> service be allowed to automatically reconfigure the firewall to allow
> a relay to run? Does the sysadmin have to configure it theirself
> (English really needs gender-neutral pronouns.)? Does anything else in
themselves, there are gender neutral pronouns in english.
> GuixSD modify the firewall at this point?
No, there are no services for iptables or nftables at this point. And
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.
The relays are just some definitions in the torrc, and that's it.
I would only ask people who currently or previously ran a tor relay,
maybe even with Guix/GuixSD, to work on this. You can't break anything,
but to test it would be good. Which is something I can't do currently.
> These all feel like rather important questions to me that need
> answering before anyone does this.
>
>
next prev parent reply other threads:[~2017-03-06 16:52 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 [this message]
2017-03-06 18:47 ` Leo Famulari
2017-03-06 20:19 ` ng0
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=20170306180030.ginyp6tywg2jcpps@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=dian_cecht@zoho.com \
--cc=guix-devel@gnu.org \
/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).