From: "Pedro J. V. Mendes" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: 45413@debbugs.gnu.org
Subject: bug#45413: Password exposure on SSH login
Date: Fri, 25 Dec 2020 12:01:36 +0000 [thread overview]
Message-ID: <5850c628-143a-4312-2fb1-b3c861a4d044@ist.utl.pt> (raw)
In-Reply-To: <m1y2hmayyb.fsf@yahoo.es>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
OK, (only) after starting with emacs -Q does the password prompt (and
the focus) appear at the mini-buffer.
On 25/12/20 11:48, Daniel Martín wrote:
> "Pedro J. V. Mendes" <pedro.mendes@ist.utl.pt> writes:
>
> [Don't forget to CC the bug tracker address so that the entire
> conversation gets tracked. Thanks.]
>
>> Hello, and happy Xmas!
>>
>> I give you snapshot of a minimal session exposing the problem.
>>
>> When I was typing the password, the characters were showing in
>> normal-face, and after pressing Enter they turned to bold-face, like
>> the previous "ssh" command.
> Do you see at the bottom of the screen a minibuffer prompt that asks for
> the password? If you enter the password in that minibuffer prompt (not
> in the shell buffer), it should replace characters with asterisks. Make
> sure you didn't accidentally switch from the minibuffer to the shell
> buffer.
>
> [Screenshot showing the problem, from the OP]
>
>
> Hm, it looks like a regular "Password:" OpenSSH prompt that should
> already be handled correctly, unless I'm missing something. Does this
> happen when you start Emacs as "emacs -Q" too?
>
>> After that both the "ssh" command and the password were recorded into
>> the history.
>>
>> I hope this helps.
>>
[-- Attachment #2: Type: text/html, Size: 1974 bytes --]
next prev parent reply other threads:[~2020-12-25 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 23:13 bug#45413: Password exposure on SSH login Pedro J. V. Mendes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-25 1:30 ` Unknown
[not found] ` <809655bd-59b7-16cc-1cb3-f45608315e44@ist.utl.pt>
2020-12-25 11:48 ` Unknown
2020-12-25 12:01 ` Pedro J. V. Mendes via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-12-25 20:45 ` Unknown
2020-12-25 20:45 ` Unknown
2020-12-25 21:29 ` João Távora
2020-12-25 21:45 ` Pedro J. V. Mendes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-25 21:59 ` João Távora
2020-12-25 22:19 ` Pedro J. V. Mendes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-28 7:21 ` Stefan Kangas
2020-12-28 10:49 ` Pedro J. V. Mendes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-27 7:03 ` Lars Ingebrigtsen
2020-12-25 1:30 ` Unknown
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=5850c628-143a-4312-2fb1-b3c861a4d044@ist.utl.pt \
--to=bug-gnu-emacs@gnu.org \
--cc=45413@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
--cc=pedro.mendes@ist.utl.pt \
/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).