all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: philipk@posteo.net, akib@disroot.org, emacs-devel@gnu.org
Subject: Re: Making package.el talk over Tor
Date: Sat, 09 Dec 2023 09:40:54 +0200	[thread overview]
Message-ID: <83y1e3ygah.fsf@gnu.org> (raw)
In-Reply-To: <E1rBobu-0001b9-TG@fencepost.gnu.org> (message from Richard Stallman on Fri, 08 Dec 2023 23:06:38 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: philipk@posteo.net, akib@disroot.org, emacs-devel@gnu.org
> Date: Fri, 08 Dec 2023 23:06:38 -0500
> 
>   > > Is this the code you mean?
>   > > 
>   > > 		      (open-network-stream
>   > > 		       name buffer host service
>   > > 		       :type gw-method
>   > > 		       ;; Use non-blocking socket if we can.
>   > > 		       :nowait (and (featurep 'make-network-process)
>   > >                                     (url-asynchronous url-current-object)
>   > >                                     '(:nowait t)))
> 
>   > > How can I make that use TOR?
> 
>   > Perhaps the ':type shell' connection is the solution?
> 
> I have no idea.  How could I use that to acheieve the goal?

I never tried this, and I'm not familiar with TOR, so all I have is
what the ELisp manual says where it documents open-network-stream
(which is the workhorse of all Emacs commands that use network
connections):

 -- Function: open-network-stream name buffer host service &rest
          parameters
     This function opens a TCP connection, with optional encryption, and
     returns a process object that represents the connection.
 [...]
     The remaining arguments PARAMETERS are keyword/argument pairs that
     are mainly relevant to encrypted connections:
 [...]
     ‘:type TYPE’
          The type of connection.  Options are:
          ‘plain’
               An ordinary, unencrypted connection.
          ‘tls’
          ‘ssl’
               A TLS (Transport Layer Security) connection.
          ‘nil’
          ‘network’
               Start with a plain connection, and if parameters
               ‘:success’ and ‘:capability-command’ are supplied, try to
               upgrade to an encrypted connection via STARTTLS.  If that
               fails, retain the unencrypted connection.
          ‘starttls’
               As for ‘nil’, but if STARTTLS fails drop the connection.
          ‘shell’
               A shell connection.
 [...]
     ‘:shell-command STRING-OR-NIL’
          If the connection ‘type’ is ‘shell’, this parameter will be
          interpreted as a format-spec string that will be executed to
          make the connection.  The specs available are ‘%s’ for the
          host name and ‘%p’ for the port number.  For instance, if you
          want to first ssh to ‘gateway’ before making a plain
          connection, then this parameter could be something like ‘ssh
          gateway nc %s %p’.

This sounds like a way to make the connection by running a shell
command.  Maybe you could arrange for using this facility to do what
you want?  Apologies if this makes no sense to someone who does
understand how TOR works; I don't.



  reply	other threads:[~2023-12-09  7:40 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  2:04 Making package.el talk over Tor Richard Stallman
2023-10-16  6:54 ` Akib Azmain Turja
2023-10-16  7:10   ` Emanuel Berg
2023-10-18  1:42   ` Richard Stallman
2023-11-17  3:53   ` Richard Stallman
2023-11-17  7:03     ` Philip Kaludercic
2023-11-19  3:39       ` Richard Stallman
2023-11-19  6:17         ` Eli Zaretskii
2023-12-09  4:06           ` Richard Stallman
2023-12-09  7:40             ` Eli Zaretskii [this message]
2023-12-13  4:58               ` Richard Stallman
2023-12-14 12:25                 ` Philip Kaludercic
2023-12-17  3:21                   ` Richard Stallman
2023-12-18  4:12                     ` Richard Stallman
2023-12-18  8:05                       ` Tomas Hlavaty
2023-12-18  8:10                         ` Tomas Hlavaty
2023-12-21  4:20                         ` Richard Stallman
2023-12-21  9:52                           ` Philip Kaludercic
2023-12-21  9:55                             ` Philip Kaludercic
2023-12-21 19:15                               ` Tomas Hlavaty
2023-12-24  3:57                               ` Richard Stallman
2023-12-24 13:36                                 ` Tomas Hlavaty
2023-12-24 15:19                                   ` Philip Kaludercic
2023-12-24 20:37                                     ` Tomas Hlavaty
2023-12-14 12:41         ` Philip Kaludercic
2023-12-14 12:54           ` Emanuel Berg
2023-12-14 13:06             ` Emanuel Berg
2023-12-17  3:21           ` Richard Stallman
2023-12-17  8:23             ` Stefan Kangas
2023-12-17  9:12               ` Eli Zaretskii
2023-12-17 12:02                 ` Never send user email address in HTTP requests Stefan Kangas
2023-12-17 12:34                   ` Eli Zaretskii
2023-12-17 14:05                     ` Yuri Khan
2023-12-17 14:44                       ` Eli Zaretskii
2023-12-17 17:30                       ` T.V Raman
2023-12-19  3:51                       ` Richard Stallman
2023-12-19  3:53               ` Making package.el talk over Tor Richard Stallman
2023-12-17 11:51             ` Philip Kaludercic
2023-12-17 14:10               ` Yuri Khan
2023-12-19  3:51                 ` Richard Stallman
2023-12-19  3:52               ` Richard Stallman
2023-12-19  3:52               ` Richard Stallman
2023-11-18  3:03     ` Richard Stallman
2023-11-18  7:21       ` Eli Zaretskii
2023-11-21  2:39         ` Richard Stallman
2023-10-16  7:12 ` Stefan Kangas
2023-10-16  9:15   ` Philip Kaludercic
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 14:22 Andrea Monaco
2023-12-18 14:29 ` Emanuel Berg
2023-12-18 14:49 ` F. Jason Park

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=83y1e3ygah.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=akib@disroot.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.