From: Eli Zaretskii <eliz@gnu.org>
To: michael.albinus@gmx.de
Cc: schwab@suse.de, 17839@debbugs.gnu.org, swiesner@lunaryorn.com
Subject: bug#17839: 24.4.50; read-passwd echoes password input in non-interactive sessions
Date: Fri, 11 Jul 2014 13:03:14 +0300 [thread overview]
Message-ID: <83zjgg9pr1.fsf@gnu.org> (raw)
In-Reply-To: <834myob55h.fsf@gnu.org>
> Date: Fri, 11 Jul 2014 12:45:14 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: schwab@suse.de, 17839@debbugs.gnu.org, swiesner@lunaryorn.com
>
> > From: Michael Albinus <michael.albinus@gmx.de>
> > Date: Fri, 11 Jul 2014 11:15:14 +0200
> > Cc: Andreas Schwab <schwab@suse.de>, 17839@debbugs.gnu.org,
> > Sebastian Wiesner <swiesner@lunaryorn.com>
> >
> > OK. There is now `read-hide-char', which triggers it. Users can let-bind
> > it to the character they prefer for hiding. This will be used in
> > `read-passwd', choosing the default ?. if it is not let-bound already.
> >
> > >> + else if (hide_chars && (c == 127)) /* DEL */
> > >> + {
> > >> + /* Unfortunately, we cannot edit stdout. */
> > >> + // fprintf (stdout, "%c", c);
> > >> + /* Hmm, this doesn't work for multi-byte characters. */
> > >> + (len > 0) && len--;
> > >> + }
> > >
> > > I don't think that's worth the trouble.
> >
> > I've removed this.
> >
> > The patch is committed to the trunk as revision 117510.
>
> Which breaks the MS-Windows build, of course, since Windows doesn't
> have termios.
I installed a temporary fix, to allow the build to succeed, but it
means that currently `read-hide-char' is a no-op on MS-Windows. Stay
tuned.
Btw, I think it's a mistake to expose termios bowels of struct
emacs_tty in minibuf.c. I think we should move that code to a
separate function in sysdep.c, which will be called from minibuf.c.
next prev parent reply other threads:[~2014-07-11 10:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 13:51 bug#17839: 24.4.50; read-passwd echoes password input in non-interactive sessions Sebastian Wiesner
2014-06-23 15:46 ` Andreas Schwab
2014-06-23 16:52 ` Sebastian Wiesner
2014-06-24 18:41 ` Glenn Morris
2014-06-24 22:55 ` Sebastian Wiesner
2014-06-25 7:47 ` Andreas Schwab
2014-06-25 8:01 ` Michael Albinus
2014-06-25 8:15 ` Andreas Schwab
2014-06-25 9:20 ` Michael Albinus
2014-06-25 9:26 ` Andreas Schwab
2014-06-25 10:03 ` Michael Albinus
2014-06-25 9:52 ` Sebastian Wiesner
2014-06-25 14:32 ` Stefan Monnier
2014-06-26 19:01 ` Glenn Morris
2014-07-10 14:36 ` Michael Albinus
2014-07-10 16:43 ` Stefan Monnier
2014-07-11 9:15 ` Michael Albinus
2014-07-11 9:41 ` Michael Albinus
2014-07-11 9:45 ` Eli Zaretskii
2014-07-11 9:58 ` Michael Albinus
2014-07-11 10:13 ` Eli Zaretskii
2014-07-11 11:32 ` Michael Albinus
2014-07-11 12:43 ` Michael Albinus
2014-07-11 14:02 ` Eli Zaretskii
2014-07-11 14:57 ` Michael Albinus
2014-07-11 15:46 ` Eli Zaretskii
2014-08-05 20:25 ` Sebastian Wiesner
2014-08-06 17:39 ` Stefan Monnier
2014-08-07 11:12 ` Sebastian Wiesner
2014-08-07 13:01 ` Stefan Monnier
2014-08-07 13:12 ` Sebastian Wiesner
2014-08-07 15:30 ` Eli Zaretskii
2014-08-07 16:08 ` Sebastian Wiesner
2014-08-07 16:38 ` Eli Zaretskii
2014-07-11 10:03 ` Eli Zaretskii [this message]
2014-07-11 10:15 ` Michael Albinus
2014-07-10 21:46 ` Sebastian Wiesner
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=83zjgg9pr1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17839@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=schwab@suse.de \
--cc=swiesner@lunaryorn.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).