From: dmandl@lehman.com (David Mandl)
To: baumbach@atmel.com
Message Hash: c50629b7e16871bdf4a9095f07df837c0178140fc1f9d3fe9f434e4dfb888a5f
Message ID: <9401041425.AA29707@disvnm2.lehman.com>
Reply To: N/A
UTC Datetime: 1994-01-04 14:29:12 UTC
Raw Date: Tue, 4 Jan 94 06:29:12 PST
From: dmandl@lehman.com (David Mandl)
Date: Tue, 4 Jan 94 06:29:12 PST
To: baumbach@atmel.com
Subject: Re: Risk and Opportunity
Message-ID: <9401041425.AA29707@disvnm2.lehman.com>
MIME-Version: 1.0
Content-Type: text/plain
> From: baumbach@atmel.com ( )
>
> [...] It seems that files are stored on disk media in fixed units
> called clusters. Your file size is usually not an integral multiple of
> disk clusters in size, so the ends of your file is followed by random
> data to fill up that last cluster. Random is a bad choice of words
> though. I suppose each system is different, but under DOS, the extra
> fill data is a copy of a piece of whatever you had in memory at the time
> your system wrote the file. You could have information written to disk
> that you do not wish to have there, and seejunk.exe will show it to you
> ... and anyone else. prune.exe is the solution offered. Using this
> program, I wrote "This space intentionally left blank " repeating in
> the 5K of space sitting at the end of the doc file for these two programs.
Yes, this is a major security hole, but the Norton Utilities has included a
program to wipe these areas clean for a while now. Of course, the Norton
Utils aren't freeware...
I've long thought that this was one of the greatest security risks in the PC
world. People tend to be sloppy about keeping this "slack area" clean. You
can easily give someone a copy of an innocent file that contains your secring
file for all to see at the end of it.
--Dave.
Return to January 1994
Return to “dmandl@lehman.com (David Mandl)”
1994-01-04 (Tue, 4 Jan 94 06:29:12 PST) - Re: Risk and Opportunity - dmandl@lehman.com (David Mandl)