unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Shuguang Sun <shuguang79@qq.com>
Cc: 35241@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#35241: 27.0.50; Tramp can't decrypt .authinfo.gpg in Win 10
Date: Tue, 16 Apr 2019 14:50:40 +0200	[thread overview]
Message-ID: <87pnpm3yhr.fsf@gmx.de> (raw)
In-Reply-To: <vk5y5zrei997.fsf@qq.com>+FB431760402C46BC (Shuguang Sun's message of "Tue, 16 Apr 2019 17:34:28 +0800")

Shuguang Sun <shuguang79@qq.com> writes:

Hi,

>>>   tramp-file-name-handler(expand-file-name "." "/plink:username@host.com:")
>>>   locate-file-internal("gpg2" (list of path) (".exe" ".com" ".bat"
>>> ".cmd" ".btm" "") 1)
>>>   executable-find("gpg2")
>>
>> This is the crucial part. `executable-find' shall operate on the local
>> file system only. But it calls `locate-file-internal' with a PATH
>> pointing to remote.
>>
>> I suppose you have edited the backtrace, and written (list of path).
>> What is there? My crystal ball tells me it contains "." ...
>
> Sorry. I do modified it here. It is the local path, not remote. And it
> contains "." which looks like:
>
>   locate-file("gpg2" ("." "C:/Users/username/emacs/bin/" "C:/Users/username/scoop/apps/gnupg/current/bin/" "C:/Users/username/scoop/shims/" "C:/Users/username/Progs/msys64/mingw64/bin/" "C:/Users/username/Progs/msys64/usr/bin/" "C:/Users/username/Progs/miktex-portable/texmfs/insta..." "C:/Users/username/AppData/Local/Microsoft/WindowsApp...") (".exe" ".com" ".bat" ".cmd" ".btm" "") 1)

Thanks, as I've expected. A relative file name like "." is the
problem. If the current directory is a remote one, it expands to a
remote directory inside exec-path, with all the hassle.

How does come "." into exec-path? Have you set this in your .emacs? Or
is it part of the PATH environment variable on your system? You know,
that it is discouraged to add "." to your PATH for security reasons.

Relative file names are not forbidden as part of exec-path. Shall we ban
them (with an error message)? Or shall we ignore them, silently? Don't know.

I'd vote for the latter (including proper documentation).

Best regards, Michael.





  parent reply	other threads:[~2019-04-16 12:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <vk5yimvkeyca.fsf@qq.com>
2019-04-16  1:20 ` bug#35241: 27.0.50; Tramp can't decrypt .authinfo.gpg in Win 10 Noam Postavsky
2019-04-16  4:54   ` Shuguang Sun
2019-04-16  7:18     ` Michael Albinus
2019-04-16  9:34       ` Shuguang Sun
2019-04-16  9:42       ` Shuguang Sun
     [not found]       ` <vk5y5zrei997.fsf@qq.com>
2019-04-16 12:50         ` Michael Albinus [this message]
2019-04-16 14:47           ` Eli Zaretskii
2019-04-16 16:20             ` Michael Albinus
2019-04-16 16:42               ` Eli Zaretskii
2019-04-16 19:42                 ` Michael Albinus
2019-04-17  7:35               ` Michael Albinus
2019-04-17 12:08                 ` Michael Albinus
2019-04-17 14:29                   ` Noam Postavsky
2019-04-17 19:09                     ` Michael Albinus
2019-04-17 17:07                   ` Eli Zaretskii
2019-04-16 15:20           ` Noam Postavsky
2019-04-16 16:03             ` Eli Zaretskii
2019-04-16 16:12               ` Michael Albinus
2019-04-17  2:02           ` Shuguang Sun
     [not found]           ` <vk5ywojt2xu2.fsf@qq.com>
2019-04-17  7:24             ` Michael Albinus
2019-04-12  2:44 Shuguang Sun

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=87pnpm3yhr.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=35241@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=shuguang79@qq.com \
    /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).