From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: ange-ftp and explicit/implicit TLS
Date: Sat, 26 Dec 2020 21:49:10 +0200 [thread overview]
Message-ID: <83r1ncl555.fsf@gnu.org> (raw)
In-Reply-To: <5d44-5fe79080-275-53124080@198151915> (david.diem@uni-konstanz.de)
> From: "David Diem" <david.diem@uni-konstanz.de>
> Date: Sat, 26 Dec 2020 20:35:09 +0100
>
> I'm trying to connect to a FTP server that requires TLS -- that is, FTPS. I learned that /bin/ftp cannot do this, so I changed ange-ftp-ftp-program-name to lftp. Ange-ftp still responds with "550 - TLS required on the control channel". In a shell outside of emacs, "lftp myuser@myserver.com" can succesfully log in (the TLS information is given on stdout) -- however, that is not the case for the command "lftp myserver.com" (without the "user@") and a subsequent "DIR" or similar. The difference of the non-emacs (non-ange-ftp) shell's output differs to that of ange-ftp in that the first says "AUTH TLS" at an early point.
>
> Is this what is called explicit TLS? How could one tell ange-ftp to say "AUTH TLS" early on? My real question, though, is why do the outputs of ange-ftp and non-ange-ftp "plain" lftp differ anyway? As I understand the ange-ftp-name-format regexp, ange starts by saying something in the form of user@server.com, that is, it does include the user right form the beginning.
If you look at defcustoms in ange-ftp.el, you will see that it allows
to customize the name of the program to use; "ftp" is just the
default. Maybe this will help you solve your problem.
prev parent reply other threads:[~2020-12-26 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 19:35 ange-ftp and explicit/implicit TLS David Diem
2020-12-26 19:49 ` Eli Zaretskii [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
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=83r1ncl555.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).