Article View: borland.public.cppbuilder.nativeapi
Article #4150Re: Locking Page in Memory
From: Eelke
Date: Fri, 10 Mar 2006 07:35
Date: Fri, 10 Mar 2006 07:35
20 lines
1873 bytes
1873 bytes
prunesquallor wrote: > Well, I guess it depends on the circumstances. If a key has been swapped out > to the swap file, then it could still be there hours, days or even weeks - > until that bit of the swap file gets overwritten. So that key is > recoverable. Whereas a key in memory expires the next time the machine's > off. > I had an idea that might work. The details I leave as an exercise. If you would use a memory mapped file the block of memory would never be written to the swapfile. Instead windows would swap it to the file. If you make sure you have the file open with exclusive access (no sharing) to the file nobody else could get access to the contents and you could zero it out when you no longer needed it. Regards, Eelke
Technical Details
Message-ID:
<44112ba0$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<440eb97d@newsgroups.borland.com> <440ec0cc@newsgroups.borland.com> <440ee584$1@newsgroups.borland.com> <4410393c$1@newsgroups.borland.com> <441046ed@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,a6a321b0cbcc9b74 X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit Date: Fri, 10 Mar 2006 08:35:56 +0100 From: Eelke <e.klein@remove.mplussoftware.nl> User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: borland.public.cppbuilder.nativeapi Subject: Re: Locking Page in Memory References: <440eb97d@newsgroups.borland.com> <440ec0cc@newsgroups.borland.com> <440ee584$1@newsgroups.borland.com> <4410393c$1@newsgroups.borland.com> <441046ed@newsgroups.borland.com> In-Reply-To: <441046ed@newsgroups.borland.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 81.58.1.162 Message-ID: <44112ba0$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1141975968 81.58.1.162 (9 Mar 2006 23:32:48 -0700) Lines: 20 Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail