aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/tty/serial/serial-tegra.c
diff options
context:
space:
mode:
authorJiri Slaby <jslaby@suse.cz>2013-02-15 15:25:05 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-02-15 10:52:36 -0800
commitb0de59b5733d18b0d1974a060860a8b5c1b36a2e (patch)
treeb304fafe3dcbb26212d95438fe2d98184752b9fc /drivers/tty/serial/serial-tegra.c
parentlguest: select CONFIG_TTY to build properly. (diff)
downloadlinux-dev-b0de59b5733d18b0d1974a060860a8b5c1b36a2e.tar.xz
linux-dev-b0de59b5733d18b0d1974a060860a8b5c1b36a2e.zip
TTY: do not update atime/mtime on read/write
On http://vladz.devzero.fr/013_ptmx-timing.php, we can see how to find out length of a password using timestamps of /dev/ptmx. It is documented in "Timing Analysis of Keystrokes and Timing Attacks on SSH". To avoid that problem, do not update time when reading from/writing to a TTY. I am afraid of regressions as this is a behavior we have since 0.97 and apps may expect the time to be current, e.g. for monitoring whether there was a change on the TTY. Now, there is no change. So this would better have a lot of testing before it goes upstream. References: CVE-2013-0160 Signed-off-by: Jiri Slaby <jslaby@suse.cz> Cc: stable <stable@vger.kernel.org> # after 3.9 is out Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/tty/serial/serial-tegra.c')
0 files changed, 0 insertions, 0 deletions