linux-kernel - Re: Reading /dev/mem by dd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1258048669.20754.1344916801@webmail.messagingengine.com>
Date:	Thu, 12 Nov 2009 15:57:49 -0200
From:	"Henrique de Moraes Holschuh" <hmh@....eng.br>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Andi Kleen" <andi@...stfloor.org>,
	"Robert Hancock" <hancockrwd@...il.com>,
	"Anton D. Kachalov" <mouse@...c.ru>, linux-kernel@...r.kernel.org
Subject: Re: Reading /dev/mem by dd

On Thu, 12 Nov 2009 17:49 +0000, "Alan Cox" <alan@...rguk.ukuu.org.uk> wrote:
> > In this case, the problem seems to be access over /dev/mem to stuff the
> > kernel is already taking care of.  Certainly "as safe as possible" does
> 
> Which is often what is desired - eg debugging driver stuff.
> 
> > not have to mean making /dev/mem useless for whatever good uses it has.
> 
> It does. Plain and simple.

Is that the only valid use of /dev/mem, or even its main use?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/