[Autogenerated] To make things.
A bit, more concrete.
Here's the list of some of the most common object types used
in user mode and the APIs or at least some of the APIs used to
access these kinds of objects.
So first, we have processes.
We've talked about processes, in the previous course,
in the these series in order to create a process.
We're going to call the create process, API that creates a process object,
that manages all the stuff within that process such as its address space,
and So on open process, is a way, to access an existing process.
So you'll find that for most object types there,
is some kind of create function.
And some kind of open function.
That will allow us to access an existing object if there's some way,
to identify it.
In the case of a process, the identification,
is based on the process,
ad which we know is used as the way to identify a process throughout the system.
As long as that process, is alive.
Similarly, we have thread objects, and we can use the create thread,
APIs We've seen in the Previous course, to create separate threads of execution.
An open thread, is an existing function as well,
that allows us to open, a handle, to an existing thread,
based on its ID job objects, are objects,
that can manage a bunch of processes as a unit,
applying various limits.
To these processes, and We've seen job objects,
in the Previous course in these series as well.
Create job object, is a way,
to create a new job object or open an Existing one based on a name,
open job object, is only about opening a handle,
to a named object, a named job object, and search information,
job, is the most important API for jobs.
That allow.
Us.
To set the limits.
That we want to set, file mapping object, call section.
In current terminology, is a way, to build,
shared memory, and map files into memory.
We've seen how to use those kinds of objects from
user mode in the previous course, in the this series for files.
This is a way, to open, a handle, to a wi or a file in the file system.
Remember the create file function, is actually short for create file object,
which means this is an abstraction, that allows us to talk,
to devices or files as one particular case,
and the most.
Common APIs there, are read, file right?
File and device, io control token objects,
are related, to the access token, to security context,
that is attached, to a process or a thread.
We've talked about that a little bit in a Previous course,
in the these series and We'll probably talk about.
That in a Future course.
So you can see some of the APIs that relate,
to tokens, a Tex,
is a synchronization primitive allows us to synchronize threads,
accessing, to a shared resource.
We look at tex access later,
in the This course when we look at threat synchronization,
event is yet.
Another kind of kernel object used, to signal something.
That interesting.
That has happened.
And We'll see examples using events later on in the these
module and Also in later parts of these co SSH four is another
kind of kernel object used for threat, sync co Organization.
We'll discuss its applicability later on in this course,
a timer, is a way,
to run some code or notify someone after a certain interval has elapsed,
Windows supports several types of timers.
This is One of those timers, that is a kernel object,
and When I say a kernel object, I mean it,
is something,
that can be used in kernel mode and in user mode Because the
object itself or objects of this type, are created in kernel space,
and this is True of all the object types we're talking about here,
all the kernel object types, that We've seen in the previous demo as well.
An io completion, port is an object,
that is used mostly to Get notified when an asynchronous IOP operation has
completed and run some piece of code if that indeed occurs.
So this is what?
Io completion, ports, are all about Windows station,
is an project object we briefly discussed in the Previous course,
in the this series where we have a management object,
which is that Windows station which sits under recession.
And manages its own other kind of resources such as desktops,
a keyboard, and an atom table, and a desktop,
is where Windows those UI elements are stored,
and That's what we typically see when we look at a Windows screen.
When we're just working with the operating system,
we've talked briefly about desktops.
In the previous course, in the this series as well.
So if you want to learn,
more some of these objects will be discussed later in this course.
But of course, these are all fully documented in the Windows SDK documentation.