3 ms·
Unnamed objects are not normally used for sharing. Naming an object is generally only done so that it can be accessed from other processes. The Windows idiom is
by barrkel 12y ago
Unnamed objects are not normally used for sharing. Naming an object is generally only done so that it can be accessed from other processes. The Windows idiom is to use a name when sharing, and don't use a name when not sharing.
I would have named these shared memory objects as a matter of course, knowing their design and purpose. That unnamed ones don't support a DACL is an interesting bit of trivia, but not much more than that. It seems more a case of non-idiomatic code.
(PS: I should be more clear here. Without using DuplicateHandle, you can't open an unnamed object, because you can't address it. It's secured by the guy who calls DuplicateHandle being in control of who he hands it off to.)