summaryrefslogtreecommitdiff
path: root/net/unix/af_unix.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-05-01 08:56:35 -0700
commit6dd4ef3051173062350a4c53a2c4212d3f052e0c (patch)
tree9354be4fe089ff36c9c5cd5d77a8f976db63c16c /net/unix/af_unix.c
parentb47833937231eebab2fe46502426ea8158fae8d9 (diff)
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>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions