From: Marcin Borkowski <mbork@mbork.pl>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: TRAMP sudo method not asking for password
Date: Wed, 16 Jan 2019 20:06:35 +0100 [thread overview]
Message-ID: <87o98gs9qc.fsf@mbork.pl> (raw)
In-Reply-To: <87k1j9sokz.fsf@gmx.de>
On 2019-01-12, at 19:44, Michael Albinus <michael.albinus@gmx.de> wrote:
> Marcin Borkowski <mbork@mbork.pl> writes:
>
> Hi all,
>
>>>> I have a very strange problem: the TRAMP sudo method stopped asking me
>>>> for the password. How is that possible? sudo in terminal behaves
>>>> normally, so it cannot be some global setting I messed up.
>>>>
>>>> emacs -Q does TRT, i.e., asks for the password.
>>>>
>>>> I understand that I can bisect my init.el, but it is almost 2 klines
>>>> long, so before I do that, I'd like to ask - maybe someone will know the
>>>> answer off the top of their head?
>>>>
>>>> Note: deleting ~/.emacs.d/tramp didn't help.
>>
>> I found it!
>>
>> My passwords were cached in ~/.authinfo. After cleaning it, TRAMP asks
>> me the password again.
>>
>> Now, this file is only mentioned once in the Emacs manual, and in
>> a different context. I think not having it even mentioned in some other
>> place is a serious security bug in the docs. Am I correct? If so, I'll
>> gladly file a bug report. (I won't try to fix it myself since I do not
>> know enough to be sure I'm doing it right.)
>
> In general, your password is written to .authinfo on demand only. That
> is, either you add a respective line, or you confirm that the
> auth-sources adds this once you have entered it interactively.
>
> The latter feature has been added to Tramp some weeks ago in Emacs 27
> (don't remember the commit date). But Tramp asks you for confirmation,
> whether you agree to add the password to your .authinfo. So you have
> answered "y"; likely by accident, w/o reading the question carefully.
Probably w/o reading it at all - I guess I just used my muscle memory to
do something after I ssh'ed somewhere with TRAMP, and didn't even bother
looking at the screen.
> And this IS documented. etc/NEWS says in the Tramp section
>
> --8<---------------cut here---------------start------------->8---
> *** Validated passwords are saved by auth-source backends which support this.
> --8<---------------cut here---------------end--------------->8---
>
> And in the Tramp manual, there is in (info "(tramp) Password handling")
>
> --8<---------------cut here---------------start------------->8---
> If there doesn’t exist a proper entry, the password is read
> interactively. After successful login (verification of the password),
> it is offered to save a corresponding entry for further use by
> ‘auth-source’ backends which support this. This could be changed by
> setting the user option ‘auth-source-save-behavior’ to ‘nil’.
> --8<---------------cut here---------------end--------------->8---
Well, I don't often read NEWS. And the above is not very clear (it says
nothing about the .authinfo file, for instance).
Don't get me wrong - I'm not just complaining. (Also, I'm very thankful
for your response!) I just think that all this info was quite easy to
miss.
To sum it up.
1. Am I the only one that thinks that this change could be made a bit
more prominent? Like using something like yes-or-no-p (as opposed to
y-or-n-p) by default, for example? Saving passwords to a plain text
file is something big, which should not happen by accident, right?
2. If others agree, what can I do to help?
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2019-01-16 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 16:36 TRAMP sudo method not asking for password Marcin Borkowski
2019-01-12 17:09 ` Marcin Borkowski
2019-01-12 17:15 ` Marcin Borkowski
2019-01-12 18:44 ` Michael Albinus
2019-01-16 19:06 ` Marcin Borkowski [this message]
2019-01-16 22:42 ` Michael Albinus
2019-01-20 5:59 ` Marcin Borkowski
2019-01-20 10:52 ` Michael Albinus
2019-01-24 17:11 ` Marcin Borkowski
2019-01-26 15:50 ` Michael Albinus
2019-01-27 15:21 ` Robert Pluim
2019-01-27 17:21 ` Michael Albinus
2019-01-28 17:53 ` Marcin Borkowski
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=87o98gs9qc.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
--cc=michael.albinus@gmx.de \
/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).