All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Andrew <nick@nick-andrew.net>
To: Madhou <madh2001@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: shell outputs anything typed when the kernel thinks@100%
Date: Fri, 4 Apr 2008 10:13:09 +1100	[thread overview]
Message-ID: <20080403231309.GB18242@tull.net> (raw)
In-Reply-To: <200803212211.43833.madh2001@gmail.com>

On Fri, Mar 21, 2008 at 10:11:43PM +0100, Madhou wrote:
> When logging in a shell, one will type his username, 'return' and then his 
> password...

It sounds like you are describing behaviour of getty, not the
shell. That's because the tty device is set to echo typed characters at
the 'login:' prompt.  After getty receives your username either it or
/bin/login will turn off the echo flag and prompt for your password.

If it's a problem for you, patch getty to turn off echo (and cooked
mode) before the 'login:' prompt and perform all keyboard input
processing and echoing in the program.

> But just after 'return' the kernel is launched into thinking for long enough 
> to the point that users who do everything fast including logging in a shell 
> let the shell display the first letters of their passwords.
> This problem tends to be critical when the user makes a demonstration to a 
> bunch of people thanks to an overhead projector.

I don't think the kernel can be blamed for this behaviour, particularly
when your password is 'qwerty'. When demonstrating, setup a demo
username so you don't have to type your own password in front of a
roomful of people.

Nick.
-- 
PGP Key ID = 0x418487E7                      http://www.nick-andrew.net/
PGP Key fingerprint = B3ED 6894 8E49 1770 C24A  67E3 6266 6EB9 4184 87E7

      parent reply	other threads:[~2008-04-03 23:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 21:11 shell outputs anything typed when the kernel thinks@100% Madhou
2008-03-21 21:31 ` Alan Cox
2008-03-21 21:37 ` Jan Engelhardt
2008-04-03 23:13 ` Nick Andrew [this message]

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=20080403231309.GB18242@tull.net \
    --to=nick@nick-andrew.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madh2001@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.