On Sun, Aug 19, 2007 at 02:31:49PM +0200, Brice Goglin wrote:
On Fri, Oct 28, 2005 at 07:47:14PM +0200, Lennert Buytenhek wrote:
On arm platforms where physical RAM doesn't start at physical address
zero, opening /dev/mem and reading from it causes a kernel oops. This
is arguably a kernel
On Mon, Sep 17, 2007 at 08:55:49AM +0200, Brice Goglin wrote:
On arm platforms where physical RAM doesn't start at physical address
zero, opening /dev/mem and reading from it causes a kernel oops. This
is arguably a kernel bug, but it's still not a very good idea to just
start
Lennert Buytenhek wrote:
The problem is not that xdm doesn't check /dev/urandom first, the
problem is that it reads from /dev/mem _at all_.
It is possible that checking /dev/urandom first masks the problem
in most configurations, but it doesn't solve it (if you don't have
/dev/random and
On Fri, Oct 28, 2005 at 07:47:14PM +0200, Lennert Buytenhek wrote:
On arm platforms where physical RAM doesn't start at physical address
zero, opening /dev/mem and reading from it causes a kernel oops. This
is arguably a kernel bug, but it's still not a very good idea to just
start randomly
Package: xdm
Severity: important
On arm platforms where physical RAM doesn't start at physical address
zero, opening /dev/mem and reading from it causes a kernel oops. This
is arguably a kernel bug, but it's still not a very good idea to just
start randomly poking around in /dev/mem in search of
5 matches
Mail list logo
