[18780] in bugtraq
Re: win32/memory locking (Re: Reply to EFS note on Bugtraq)
daemon@ATHENA.MIT.EDU (James Perry)
Wed Jan 24 11:53:24 2001
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.LNX.4.30.0101240908510.813-100000@grail.dhs.org>
Date: Wed, 24 Jan 2001 09:15:01 +0000
Reply-To: James Perry <jeperry@UWATERLOO.CA>
From: James Perry <jeperry@UWATERLOO.CA>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To: <20010123150901.A22134@usa.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Bits _never_ get written to the disk? Guaranteed never to use swap space?
>
> The GnuPG FAQ (http://www.gnupg.org/faq.html#q6.1) suggests that it is
> not possible to make a Windows program insist on physical RAM the way a
> program can in Open Systems. Does EFS really use only physical RAM? If
> so, is there some win32 API that can be used by other application designers
> who want to guarantee that certain blocks of allocated memory are *never*
> swapped out to disk? The most likely candidate I've come across is
> VirtualLock() which, unfortunately, "does not mean that the page will not be
> paged to disk" (http://msdn.microsoft.com/library/techart/msdn_virtmm.htm).
>
> Thanks,
>
> -Peter
>
As described on the MSDN site:
"The AllocateUserPhysicalPages function is used to allocate physical
memory. Memory allocated by this function must be physically present in
the system. Once allocated, it is locked down and unavailable to the rest
of the virtual memory management system of Windows 2000."
_http://msdn.microsoft.com/library/psdk/winbase/memman_0u5v.htm_
The UserPhysicalPages class of functions appear to be directly related to
kernel calls, so I'd take a guess and say it's probably what you're
looking for.
- James Perry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/
iD8DBQE6bp0ds6J9OMPOxE8RAki4AKCiTWweQkkvcRWBqUyXJDQEFu8yngCfYNP8
f/adsAYRzRYstL63pJZSZbo=
=g2j5
-----END PGP SIGNATURE-----
