Re: Locking physical memory (RAM) under Windows

Ben Laurie (ben@algroup.co.uk)
Sun, 28 Jun 1998 20:55:39 +0100

• Next message: Dwcpride@aol.com: " "
• Previous message: Simon R Knight: "386spart.par win386.swp"

Simon R Knight wrote:
> When drivers are available which can *reliably* lock data in RAM,
> then developing a more secure range of edit controls sounds like an
> interesting project. Can any real security be had while using
> Windows character-set/fonts though ?

Since no drivers have been forthcoming so far, I spent a little while
poking around in the DDK and musing as to whether I had the time and
energy to have a crack at this myself, when I came across VirtualLock().
I've seen no mention of this before, so I'm wondering whether anyone has
tried it, and whether it actually works as it claims. I quote the manual
page:

"The VirtualLock function locks the specified region of the process's
virtual address space into memory"

NT only, I'm afraid, but if it does work at least we cut down the device
driver requirement to just Win95, right?

Cheers,

Ben.

-- 
Ben Laurie            |Phone: +44 (181) 735 0686| Apache Group member
Freelance Consultant  |Fax:   +44 (181) 735 0689|http://www.apache.org/
and Technical Director|Email: ben@algroup.co.uk |
A.L. Digital Ltd,     |Apache-SSL author     http://www.apache-ssl.org/
London, England.      |"Apache: TDG" http://www.ora.com/catalog/apache/
WE'RE RECRUITING! http://www.aldigital.co.uk/recruit/

• Next message: Dwcpride@aol.com: " "
• Previous message: Simon R Knight: "386spart.par win386.swp"