lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200803212211.43833.madh2001@gmail.com>
Date:	Fri, 21 Mar 2008 22:11:43 +0100
From:	Madhou <madh2001@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: shell outputs anything typed when the kernel thinks@...%

Kernel: 2.6.21.5
OS: Slackware12.0


This is a long time annoying misconception i'm reporting here:

When a command is run from a shell and drives the kernel to use 100% of cpu 
for a while, linux lets printing on screen anything that is typed.
This doesn't sound too much annoying at first sight, but actually this 
confronts the users to a problem:
When logging in a shell, one will type his username, 'return' and then his 
password...
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.

The time that the kernel takes for checking usernames is about one second on 
my laptop which is equipped with an intel centrino 1,7GHz.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ