This is what I had to do also, creating the event in user space and pass the
handle to the driver. I remember some MSJ article describing this as the
suggested approach. Creating the event as a driver only seems to work if
you are a service, or have administrator rights.
PJ
-----Original Message-----
From: Johnny [mailto:xxxxx@yahoo.de]
Sent: Friday, May 03, 2002 9:31 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Security Attributes on a Notification Event created
at Kernel level
On simpler solution would be to create an named event in your app and open
the same event in the kernel. In this case you can do any thing with it in
kernel and user mode
Johnny
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Daniel Simard
Sent: Freitag, 3. Mai 2002 15:09
To: NT Developers Interest List
Subject: [ntdev] Security Attributes on a Notification Event created at
Kernel level
Abstract:
Does someone know if it is possible to have full access on a Notification
Event created in a Kernel driver?
Summary:
- In a driver, I created a named event with IoCreateNotificationEvent
function. - In an Application, I openned this event with OpenEvent function
- I can only open the event with OpenEvent(SYNCHRONIZE, FALSE,
szEventName), which give me access to test and wait the event. If I try
OpenEvent(EVENT_ALL_ACCESS, FALSE, szEventName), I get an access denied on
the open function.
Questions:
Is there some calls I could do at kernel level that will enable my
application to have SetEvent, ResetEvent permissions on the event? Are
there security attributes on the event?
You are currently subscribed to ntdev as: xxxxx@yahoo.de
To unsubscribe send a blank email to %%email.unsub%%
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
You are currently subscribed to ntdev as: xxxxx@funk.com
To unsubscribe send a blank email to %%email.unsub%%