[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111109224954.3864c426@lxorguk.ukuu.org.uk>
Date: Wed, 9 Nov 2011 22:49:54 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Greg KH <greg@...ah.com>
Cc: Vasiliy Kulikov <segoon@...nwall.com>, Eugene Teo <eugeneteo@...nel.sg>,
security@...nel.org, kernel-hardening@...ts.openwall.com,
linux-kernel@...r.kernel.org
Subject: Re: kernel: multiple flaws allowing to sniff keystrokes timings
> > 1) show zero fields to unprivileged users (for /proc/interrupts and
> > /proc/stat it is CAP_SYS_ADMIN, for /proc/$PID/{stat,sched,schedstat} it
> > is ptrace_may_access(), for ttys it is uid check) and real values for
> > privileged. The same technique is used in /proc/$PID/sched for eip/esp
> > values.
>
> That makes sense to a point, users will wonder why they aren't seeing
> interrupts anymore, which is a valuable debug tool.
For the interrupts case you don't want show misleading data. It really
has only one use so it's better to change the permissions in the
hardening case. Something distros can already do
> All that is leaking here is the number of keystrokes at most, right?
If even that on USB.
> If we provide a "good" library function for keyboard password usage, we
> could get other applications to use it, but yes, it is a tough issue :(
You can also create noise by rounding off the values a bit. I don't think
it would need much rounding to keep useful data and fuzz, and the
rounding factor can be stuck in sysfs and default to 0.
Alan
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
