Right, haven't thought of that. It's a good thing I ran into that perceived problem with mach_destroy_memory_entry or I would have thought my solution was secure. Thanks again for your help! On Thu, 1 Jul 2004 12:10:33 -0400, Jim Magee <jmagee@apple.com> wrote:

Now, lets assume that while the client DID have access, it sends some

portion of that memory contents to some other server "copy-on-write."

Or it makes twelve [shared] copies of it in his own address space. Or

it requests some form of long-term IOKit UserClient direct I/O to the

memory. You have no control over any of this - regardless of the

design of your server.

_______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.