{"push_id":1223459349,"size":1,"distinct_size":1,"ref":"refs/heads/6.0.1","head":"4a275656c72ff326c9212d9816c5ada2a3e6ba6a","before":"59a982871e2a43b281df07f249b0797d19e017d5","commits":[{"sha":"4a275656c72ff326c9212d9816c5ada2a3e6ba6a","author":{"name":"Jiri Slaby","email":"5983af6a8e8283aa60de579a10bd4a0e541489a0@suse.cz"},"message":"TTY: do not update atime/mtime on read/write\n\ncommit b0de59b5733d18b0d1974a060860a8b5c1b36a2e upstream.\n\nOn http://vladz.devzero.fr/013_ptmx-timing.php, we can see how to find\nout length of a password using timestamps of /dev/ptmx. It is\ndocumented in \"Timing Analysis of Keystrokes and Timing Attacks on\nSSH\". To avoid that problem, do not update time when reading\nfrom/writing to a TTY.\n\nI am afraid of regressions as this is a behavior we have since 0.97\nand apps may expect the time to be current, e.g. for monitoring\nwhether there was a change on the TTY. Now, there is no change. So\nthis would better have a lot of testing before it goes upstream.\n\nReferences: CVE-2013-0160\n\nSigned-off-by: Jiri Slaby <jslaby@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/4a275656c72ff326c9212d9816c5ada2a3e6ba6a"}]}
{"actor":{"display_login":"dblockopp"}}