unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 56518@debbugs.gnu.org
Subject: bug#56518: Drop rsh/rlogin/remsh from Ange FTP
Date: Tue, 12 Jul 2022 17:13:23 +0200	[thread overview]
Message-ID: <87pmia74a4.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmmoY7GqQihiswgae6AXxQmYL7HvfHhyR4aNfUjwYpFOWg@mail.gmail.com> (Stefan Kangas's message of "Tue, 12 Jul 2022 09:55:12 -0500")

Stefan Kangas <stefan@marxist.se> writes:

Hi Stefan,

> Assuming that Ange FTP is still relevant these days, its documentation
> should not be talking about using "rsh", "rlogin" and "remsh" (as they
> are obsolete).  Please rewrite its documentation to talk about SSH
> instead.

These programs are mentioned in relation to "gateways". That is, if you
cannot access the FTP server from your local machine, you can connect to
that gateway (via rsh or alike) and start the ftp client on that
machine.

I guess we shall remove gateways at all from ange-ftp.el, because I
don't know whether they work with ssh or friends. At least, they shall
be made obsolete.

A proper replacement would be to improve Tramp's multi-hop, and support
remote file names like "/ssh:gateway|ftp:server:/path/to/file". Anything
goes, but is it really worth the trouble? It won't be trivial.

OTOH, I have no idea whether there's still somebody using Ange FTP with
gateways.

> (I note that Firefox and Chrome dropped FTP support in 2021.
> And the FSF has sunset their FTP servers.)

Sigh.

Best regards, Michael.





  reply	other threads:[~2022-07-12 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 14:55 bug#56518: Drop rsh/rlogin/remsh from Ange FTP Stefan Kangas
2022-07-12 15:13 ` Michael Albinus [this message]
2022-07-12 15:48 ` Eli Zaretskii
2022-07-13  9:53   ` Michael Albinus
2022-07-13 10:09     ` Robert Pluim
2022-07-13 10:38       ` Michael Albinus
2022-07-13 11:52       ` Eli Zaretskii
2022-07-13 12:01       ` Visuwesh

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmia74a4.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=56518@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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/emacs.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).