The documentation repeatedly states that "windows_shared_memory has no kernel persistence and is destroyed when all processes using that shared memory are gone." But I'm trying to find out what exactly is used for the implementation of winows_shared_memory? Is it implemented internally as a Windows named pipe? Is it based on using ReadProcessMemory? Anyone know? Brent Arias Software Architect Lumension Security(tm) Tel ~ (602) 692-8088 Fax ~ (480) 970-6323 brent.arias@lumension.commailto:brent.arias@lumension.com
Brent Arias wrote:
The documentation repeatedly states that "windows_shared_memory has no kernel persistence and is destroyed when all processes using that shared memory are gone."
But I'm trying to find out what exactly is used for the implementation of winows_shared_memory? Is it implemented internally as a Windows named pipe? Is it based on using ReadProcessMemory? Anyone know?
I believe it's based on CreateFileMapping.
Andrew Holden wrote:
Brent Arias wrote:
The documentation repeatedly states that "windows_shared_memory has no kernel persistence and is destroyed when all processes using that shared memory are gone."
But I'm trying to find out what exactly is used for the implementation of winows_shared_memory? Is it implemented internally as a Windows named pipe? Is it based on using ReadProcessMemory? Anyone know?
I believe it's based on CreateFileMapping.
Yes, it's implemented with the native windows shared memory, but using the system paging file instead of by a file in the file system. See: http://msdn.microsoft.com/en-us/library/aa366537(VS.85).aspx
participants (3)
-
Andrew Holden
-
Brent Arias
-
Ion Gaztañaga