TTY: do not update atime/mtime on read/write
authorJiri Slaby <jslaby@suse.cz>
Fri, 15 Feb 2013 14:25:05 +0000 (15:25 +0100)
committerBen Hutchings <ben@decadent.org.uk>
Mon, 13 May 2013 14:02:31 +0000 (15:02 +0100)
commitc29ad805df8c54a9f5d74c66bf5d4a2d449bd99a
tree66f22e0b2366a709662c7be5a46248d8a652aa23
parent268a8c92cb70b59d71e51c22c20f7aac45971391
TTY: do not update atime/mtime on read/write

commit b0de59b5733d18b0d1974a060860a8b5c1b36a2e upstream.

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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/tty/tty_io.c