From: Jean Pierre De Jesus DIAZ via Guix-patches via <guix-patches@gnu.org>
To: "47155@debbugs.gnu.org" <47155@debbugs.gnu.org>
Cc: "raid5atemyhomework@protonmail.com"
<raid5atemyhomework@protonmail.com>,
Maxime Devos <maximedevos@telenet.be>
Subject: [bug#47155] [PATCH] gnu: Respect DataDirectoryGroupReadable option of tor.
Date: Tue, 27 Dec 2022 11:52:55 +0000 [thread overview]
Message-ID: <wWWacY1yGL7QOEduL6elaZGKFwOPnxeA4z7fRnJTYUA1pqj3cLZdyA5-63eVCN_3LYn3rKwofeHyvcBMeDKzBtnC7xNabWY-K8JtZrtjrKM=@jeandudey.tech> (raw)
In-Reply-To: <z7bo5cNBBIFwYrhxbJfvgpqSV8WXpQlpP9NKuZkyGvuXUP7iVJ86yHGgPuVlYgAmxas9QM_VF6XBy5AiktHlNubv_a6RMMwqIisIFzMHW7A=@protonmail.com>
>+ (when #$control-port?
>+ (format port
>+ "\
>+ControlPort ~a
>+CookieAuthentication 1
>+CookieAuthFileGroupReadable 1
>+DataDirectoryGroupReadable 1\n"
Maybe instead of a port, we can have separate options for `control-port',
and `cookie-authentication?'. As IIUC cookie authentication can still be
used with a control UNIX domain socket.
>+ #$(if (eq? control-port? #t)
>+ 9051
>+ control-port?)))
As a side note, the `if' can be removed and the port put in place into
the string directly. But would prefer an option in the configuration
record for the control port.
—
Jean-Pierre De Jesus DIAZ
prev parent reply other threads:[~2022-12-27 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 11:15 [bug#47155] [PATCH] gnu: Respect DataDirectoryGroupReadable option of tor raid5atemyhomework via Guix-patches via
2021-03-15 16:35 ` Maxime Devos
2021-03-15 23:42 ` raid5atemyhomework via Guix-patches via
2021-03-27 6:37 ` raid5atemyhomework via Guix-patches via
2021-03-27 9:45 ` Maxime Devos
2021-03-27 11:06 ` raid5atemyhomework via Guix-patches via
2021-03-27 12:13 ` Maxime Devos
2021-07-23 15:07 ` raid5atemyhomework via Guix-patches via
2022-12-27 11:52 ` Jean Pierre De Jesus DIAZ via Guix-patches via [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='wWWacY1yGL7QOEduL6elaZGKFwOPnxeA4z7fRnJTYUA1pqj3cLZdyA5-63eVCN_3LYn3rKwofeHyvcBMeDKzBtnC7xNabWY-K8JtZrtjrKM=@jeandudey.tech' \
--to=guix-patches@gnu.org \
--cc=47155@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=me@jeandudey.tech \
--cc=raid5atemyhomework@protonmail.com \
/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.