From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: Re: documentation/behavior unclear of (tor-hidden-service)
Date: Sat, 4 Mar 2017 16:21:26 +0000 [thread overview]
Message-ID: <20170304162126.urcuuh6b5wg3eequ@abyayala> (raw)
In-Reply-To: <20170304155916.slok53nrcporwwat@abyayala>
On 17-03-04 15:59:16, ng0 wrote:
> I have a question regarding the (tor-hidden-service) service.
>
> When I have an previously generated hostname, let's call it
> "fooschnickens1234.onion" for the purpose of this message, my approach
> on a system like Gentoo was to manually place the hostname and
> private-key into the /var/lib/tor/hidden-services/$name-i-gave-in-torrc
> folder and change the permissions afterwards.
>
> Now this service is unclear about wether it would overwrite the files I
> have when the new system generation is done building (reconfigure).
>
> It would be good to know wether the files can be copied into place in
> advance or if one has to wait to replace it afterwards.
>
Okay, be your own testpilot:
A quick 'guix system build config.scm' and before reconfiguring
inserting my values into the then new generated
/var/lib/tor/hidden-services/foo/ and the files in there, then running
reconfigure, rebooting and I can connect to my hostname(s).
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"?
next prev parent reply other threads:[~2017-03-04 15:12 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 [this message]
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
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=20170304162126.urcuuh6b5wg3eequ@abyayala \
--to=contact.ng0@cryptolab.net \
--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.