unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nigko Yerden <nigko.yerden@gmail.com>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Florian Pelz <pelzflorian@pelzflorian.de>,
	70341-done@debbugs.gnu.org
Subject: bug#70341: [PATCH v9] services: tor: Add support for pluggable transports.
Date: Mon, 14 Oct 2024 13:41:08 +0200	[thread overview]
Message-ID: <87msj63oa3.fsf@gnu.org> (raw)
In-Reply-To: <cc8e1a7d003c536a5630fd5c806087b55dcc267a.1728236348.git.nigko.yerden@gmail.com> (Nigko Yerden's message of "Sun, 6 Oct 2024 22:39:08 +0500")

Hi,

Nigko Yerden <nigko.yerden@gmail.com> skribis:

> Pluggable transports are programs that disguise Tor traffic, which
> can be useful in case Tor is censored.  Pluggable transports
> cannot be configured by #:config-file file exclusively because Tor
> process is run via 'least-authority-wrapper' and cannot have access
> to transport plugin, which is a separate executable (Bug#70302,
> Bug#70332).
>
> ;;; Copyright © 2024 Nigko Yerden <nigko.yerden@gmail.com>
>
> * doc/guix.texi (Networking Services): Document 'tor-transport-plugin'
> data type and 'transport-plugins' option for 'tor-configuration.
> * gnu/services/networking.scm: Export
> 'tor-configuration-transport-plugins', 'tor-transport-plugin',
> 'tor-transport-plugin?', 'tor-plugin-role',
> 'tor-plugin-protocol', and 'tor-plugin-program'.
> (<tor-configuration>): Add 'transport-plugins' field.
> (<tor-transport-plugin>): New variable.
> (tor-configuration->torrc): Add content to 'torrc' computed-file.
> (tor-shepherd-service): Add file-system-mapping(s).
>
> Change-Id: I1b0319358778c7aee650bc843e021a6803a1cf3a

Finally applied, thanks!

Ludo’.




  reply	other threads:[~2024-10-14 12:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 14:48 [bug#70341] [PATCH] gnu: Add support for pluggable transports to tor-service-type Nigko Yerden
2024-04-20 14:43 ` [bug#70341] [PATCH v2] services: tor: Add support for pluggable transports Nigko Yerden
2024-04-22  3:58 ` [bug#70341] [PATCH v3] " Nigko Yerden
     [not found]   ` <Zil1buljj2AfL2zL@andel>
2024-04-25  6:08     ` Nigko Yerden
2024-04-30  9:13       ` Nigko Yerden
2024-05-10  8:32 ` [bug#70341] [PATCH v4] " Nigko Yerden
2024-05-23 21:49   ` André Batista
2024-05-31  5:43 ` [bug#70341] [PATCH v5] " Nigko Yerden
2024-07-11 13:27 ` [bug#70341] [PATCH v6] " Nigko Yerden
2024-08-09  9:15 ` [bug#70341] [PATCH v7] " Nigko Yerden
2024-09-04 14:08   ` Ludovic Courtès
2024-09-17 13:11 ` [bug#70341] [PATCH v8] " Nigko Yerden
2024-10-06 17:39 ` [bug#70341] [PATCH v9] " Nigko Yerden
2024-10-14 11:41   ` Ludovic Courtès [this message]
2024-10-14 16:36     ` Nigko Yerden
2024-10-15  6:26     ` Nigko Yerden
2024-10-15 15:43       ` Ludovic Courtès

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=87msj63oa3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=70341-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=nigko.yerden@gmail.com \
    --cc=pelzflorian@pelzflorian.de \
    /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).