edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Disabling local echo for password fields
Date: Mon, 3 Jul 2017 07:19:27 +0200	[thread overview]
Message-ID: <20170703051927.GA1994@nautica> (raw)

Hi all,


(I'm new here, just recently found out about edbrowse and I like the
concept)


This discussion started on github, I will write a short recap for people
not following github issues: https://github.com/CMB/edbrowse/pull/29


Basically, I'd like to disable local echo to keep passwords for
appearing in plain text, so people in the same room will not be able to
glance over my shoulder.
This is consistent with most unix login utilities (initial login, ssh
password prompt, etc)

One of the issue that was raised is that I only made the change for HTTP
auth, but that leaves many password input fields visible so it is a very
incomplete fix.


There are two sides to input fields:
 - the input itself, as things stand, small input fields have to be
entered as a full line e.g. i2=mypass, which cannot be easily hidden as
we read lines one at a time.
CMB suggested adding a new input function, for example 'pi' for 'private
input', that would prompt for the content of the input box and could be
more easily hidden.
If the extra command is a burden, we could make 'i' work again in browse
mode, and decide if there should be local echo based on the input field
type=password

 - the input content printed back out when you display the buffer
content, e.g. 'p' after entering.
This text could be starred out, either based on type=password, or if a
new command is implemented we could just always display stars whenever
that private input command is used (as the user likely would not want
the input of these commands printed)


What are others thoughts of adding such a command?

I like the idea and don't see much downsides, anyone wanting to use
i2=pass still can if they want to and it would be appropriate.
It might be slightly more confusing for new users but I think the
concept of no-echo is common enough in the unix world, I'm not too sure
about windows.



Other points that were addressed:
 - windows users will need a different way to disable echo, I'm not
familiar with windows terminal/input window at all, but I understand the
need. I will split the linux tcsetattr code in a subfunction that will
need a windows equivalent.

 - there is a second patch about adding CURLAUTH_NEGOTIATE back as an
option as I would use it, Adam Thompson disabled it back in 2014;
waiting for his or anyone's input if it is still useful to keep disabled
by default or not.


Thank you for reading,
-- 
Dominique Martinet | Asmadeus

             reply	other threads:[~2017-07-03  5:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  5:19 Dominique Martinet [this message]
2017-07-03 11:29 ` Karl Dahlke
2017-07-07 12:13   ` Chris Brannon
2017-07-07 13:35     ` Dominique Martinet
2017-07-09 14:40   ` Dominique Martinet
2017-07-09 15:45     ` Karl Dahlke
2017-07-09 21:45     ` Karl Dahlke
2017-07-10  4:56       ` Dominique Martinet
2017-07-11  4:32         ` Chris Brannon
2017-07-12  6:11           ` Dominique Martinet
2017-07-12 12:27             ` Chris Brannon
2017-07-12 12:55               ` Dominique Martinet
2017-07-12 14:32                 ` Chris Brannon
2017-07-12 15:02                   ` Dominique Martinet
2017-07-12 22:00                     ` Chris Brannon
2017-07-12 16:56                   ` Karl Dahlke
2017-07-12 12:44             ` Karl Dahlke
2017-07-15 11:29               ` Dominique Martinet
2017-07-15 12:27                 ` Chris Brannon
2017-07-15 23:42                   ` Karl Dahlke
2017-07-16  2:22                 ` Chris Brannon
2017-07-17 14:04                 ` Chris Brannon
2017-07-17 14:39                   ` Dominique Martinet
2017-07-17 14:45                     ` Chris Brannon

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170703051927.GA1994@nautica \
    --to=asmadeus@codewreck.org \
    --cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).