* ram device not initialised to zero in 2.4.8
@ 2001-08-23 21:53 Peter T. Breuer
2001-08-23 23:53 ` Sandip Bhattacharya
0 siblings, 1 reply; 2+ messages in thread
From: Peter T. Breuer @ 2001-08-23 21:53 UTC (permalink / raw)
To: linux kernel
I don't see what harm it does, but the ram devices are full of
interesting data if you read them after setting them up. Either
this is a security hole waiting to happen, or somebody is being
very inventive with the fill ...
I did
mke2fs -m0 /dev/ram2 4096
dd if=/dev/ram2 | od -a | less
and had a good read.
Peter
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: ram device not initialised to zero in 2.4.8
2001-08-23 21:53 ram device not initialised to zero in 2.4.8 Peter T. Breuer
@ 2001-08-23 23:53 ` Sandip Bhattacharya
0 siblings, 0 replies; 2+ messages in thread
From: Sandip Bhattacharya @ 2001-08-23 23:53 UTC (permalink / raw)
To: linux-kernel
On Thu, Aug 23, 2001 at 11:53:43PM +0200, Peter T. Breuer merrily said:
> I don't see what harm it does, but the ram devices are full of
> interesting data if you read them after setting them up. Either
> this is a security hole waiting to happen, or somebody is being
> very inventive with the fill ...
Well. It would probably be the first possibility. I tried out what you
said, and it showed me the contents of a mail which I had just sent
out ...
- Sandip
--
-------------------------------------
Sandip Bhattacharya
sandipb @ bigfoot.com
http://www.sandipb.net
-------------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-08-23 23:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-08-23 21:53 ram device not initialised to zero in 2.4.8 Peter T. Breuer
2001-08-23 23:53 ` Sandip Bhattacharya
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox