[Autogenerated] Using named objects, is one of the easiest ways,
to share, kernel objects between processes as we've seen already.
However, there, is a downside, and that downside,
is that these names, are visible.
So it's possible for a malicious, entity to utilize that power to get a handle,
to the same object, and then foil it in some way,
to cause some kind of their behavior As we've seen
the example with media player, can we have some kind of private object,
namespace that would allow us to share objects by name
but still not make these names visible,
to other processes which should not be sharing those objects.
And the answer, is Yes, this is a feature called private object,
namespace which I've mentioned already.
That was implemented in vista initially,
and we can use certain APIs to build,
a private namespace which will never be visible from user mode no matter what.
So this is the idea the object names, are essentially invisible.
And Even in cross explorer, they will have these kind of weird names.
That are not something you can take advantage of.
It's also possible.
To even restrict the seeds or security IDs and even something called
integrity level which we want to be discussing in,
in this course,
that would further restrict the possibility of using those namespace or
namespace we're creating for hosting our privately named objects.
Let's see an example of what that looks like.