PKEVENT
IoCreateNotificationEvent(
IN PUNICODE_STRING EventName,
OUT PHANDLE EventHandle
);
Or
PKEVENT
IoCreateSynchronizationEvent(
IN PUNICODE_STRING EventName,
OUT PHANDLE EventHandle
);
The two DOCUMENTED interfaces for creating named events from a driver are at
least one parameter each short of having an interface that specifies the
security on the object. So, as my original point stated, if you create the
event in the driver then you have to go fix up the security before it is
actually usable from a normal application.
I note also that the ddk says: “The preferred method to share event objects
between user mode and kernel mode is for the user-mode program to create the
event object and pass it to the driver through an IOCTL.”
The object security api documented in the DDK is pathetic. You can grovel
around the include files to discover what is actually available, or go and
purchase the IFS kit for a few more clues, or as the DDK suggests go and
read the Platform SDK (with a translation filter) to get a clue as to how to
actually go about changing the security on the event you created using one
of the above apis, but that all seems rather a lot of work, when the
original poster could simply pend an irp instead.
-----Original Message-----
From: Cunningham, Owen [mailto:xxxxx@fmr.com]
Sent: Wednesday, November 21, 2001 2:59 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Setting a user mode visible event from kernel mod e
driver
Correct me if I’m wrong, but in any event, aren’t these statements true only
if a NULL security descriptor is passed into the object’s create call? If
you’re willing to build a security descriptor with the desired ACLs, you
should be all set from the beginning.
-----Original Message-----
From: Peter Viscarola [SMTP:xxxxx@osr.com]
Sent: Wednesday, November 21, 2001 12:42 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Setting a user mode visible event from kernel
mod e driver“Roddy, Mark” wrote in message
> news:xxxxx@ntdev…
> >
> > At least in nt4, if you create the event from the driver the
> > security on
> it
> > will be obnoxious to the application.
> >
>
> Or not, depending on the application’s access rights. Easily solved
> by changing the access rights on the object. This is the same problem
> that you’d have if you create the object from a service during system
> startup.
>
> Peter
> OSR
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@fmr.com To
> unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com