unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: unable to visit /ftp:USER@MACHINE.com:~
Date: Fri, 11 Aug 2017 18:23:26 +0200	[thread overview]
Message-ID: <87378y2hvl.fsf@len> (raw)

Dear emacs users,

I'm unable to visit /ftp:USER@MACHINE.com:~
although there is a line

machine  MACHINE.com port ftp  login USER     password "PASSWORD"

in my ~/.authinfo.gpg

with the correct infos instead of the capitalised parts.

This is no configuration issue, since this:

EMACS -Q -nw --eval "(setq auth-source-debug 'trivia)" --eval '(setq ange-ftp-netrc-filename "~/.authinfo.gpg")'   /ftp:USER@MACHINE.com:~

does not work for emacs24, emacs25 and emacs-snapshot (emacs from
git as of today) as values of EMACS.  I'm asked by gpg-agent for
my passphrase to the key which decrypts ~/.authinfo.gpg and
actually I am able to visit this file and see it's decrypted
content.

Without setting ange-ftp-netrc-filename I'm not asked by
gpg-agent but instead emacs asks me for the password of
USER@MACHINE.com.


but the result is otherwise the same (besides the line regarding
authinfo.gpg):


*Messages*:
For information about GNU Emacs and the GNU system, type C-h C-a.
Decrypting /home/grfz/.authinfo.gpg...done
Opening FTP connection to ha01s001.org-dns.com...
tramp-file-name-handler: FTP Error: OPEN request failed: open ha01s001.org-dns.com



*ftp USER@MACHINE.com*
ftp> open ha01s001.org-dns.com
open ha01s001.org-dns.com
Connected to ha01s001.org-dns.com.
220 ProFTPD 1.3.5b Server (ProFTPD) [212.144.99.144]
234 AUTH TLS successful
[SSL Cipher ECDHE-RSA-AES256-GCM-SHA384]
200 PBSZ 0 successful
200 Protection set to Private
[Encrypted data transfer.]
ftp>

If I then type ls in the *ftp USER@MACHINE.com* (Internal
Ange-ftp:run) buffer I get:

ftp> ls
ls
530 Please login with USER and PASS
ftp: bind: Address already in use
ftp>

This is on debian 9.1 (stretch) with ftp provided by package
ftp-ssl:

~$ type -a ftp
ftp is /usr/bin/ftp
~$ ls -l /usr/bin/ftp
lrwxrwxrwx 1 root root 21 Jul  1 15:38 /usr/bin/ftp -> /etc/alternatives/ftp*
~$ ls -l /etc/alternatives/ftp
lrwxrwxrwx 1 root root 16 Jul  1 15:38 /etc/alternatives/ftp -> /usr/bin/ftp-ssl*
~$ file /usr/bin/ftp-ssl
/usr/bin/ftp-ssl: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=e7426e29e339b8432948fadea38cf0137e6b3e62, stripped
~$





Any ideas how to make emacs/tramp connect to this ftp site?

Thanks for your reading, Gregor




             reply	other threads:[~2017-08-11 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 16:23 Gregor Zattler [this message]
2017-08-13  8:57 ` unable to visit /ftp:USER@MACHINE.com:~ Michael Albinus
2017-08-13 10:56   ` Gregor Zattler
2017-08-14 16:21     ` Michael Albinus
2017-08-14 21:47       ` Gregor Zattler
2017-08-15  3:36         ` Michael Albinus
2017-08-16 10:01         ` Michael Albinus
2017-08-16 22:38           ` Gregor Zattler
2017-08-17 21:59             ` Gregor Zattler

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=87378y2hvl.fsf@len \
    --to=telegraph@gmx.net \
    --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).