From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: documentation/behavior unclear of (tor-hidden-service)
Date: Mon, 06 Mar 2017 16:45:28 +0100 [thread overview]
Message-ID: <87lgsis92f.fsf@gnu.org> (raw)
In-Reply-To: <20170306120820.libvu2akv34jmrrd@abyayala> (ng0's message of "Mon, 6 Mar 2017 12:08:20 +0000")
ng0 <contact.ng0@cryptolab.net> skribis:
> On 17-03-06 11:13:32, Ludovic Courtès wrote:
>> Hi!
>>
>> ng0 <contact.ng0@cryptolab.net> skribis:
>>
>> > moving on, this could be improved:
>> > In case one aims for keeping the config public this is a bad idea but
>> > what about creating the hostname + private_key in $name as plain-file?
>> > Would this be overwritten by (tor-hidden-service) or would this just be
>> > bad practice but "whatever works for you"?
>>
>> Tor is stateful here: it creates the
>> /var/lib/tor/hidden-services/SERVICE directory once, and then never
>> touches it again.
>>
>> Do you think our documentation should be improved? Could you suggest a
>> patch that improves things, while at the same time not paraphrasing too
>> much of Tor’s own documentation?
[...]
> What do you think about the private-key + hostname option? Too much
> of bad practice to implement it for the service?
What do you mean?
Now that I checked, I see the documentation explains exactly what I
wrote above, with a link to upstream’s documentation for details. What
should we add?
> I was thinking of adding a (tor-relay-node) once I have the option to
> run a GuixSD system not in my home and/or other circumstances are
> solved which now prevent certain things.
Would be nice.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-03-06 15:45 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgsis92f.fsf@gnu.org \
--to=ludo@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.