Reg. IRP_MJ_SET_SECURTIY

NTDEV
1

Hi all,
The IRP_MJ_SET_SECURTIY has a PSECURITY_DESCRIPTOR in its IoStackLocation’
parameters.

Can anybody tell me what is the data in the buffer at which the pointer is
pointing??

Is there in way in which we can extract the data stored at the buffer at
which this pointer is pointing?

Also is it possible if we can create our own security descriptor, fill in
the buffer & pass it to the lower level driver?

Thanks

2

Reg. IRP_MJ_SET_SECURTIYIts an opaque data type. However, if you look up in
the PlatformSdk and the MSDN documentation you should find enough
information to understand what is in this structure.

Replacing the input PSECURITY_DESCRIPTOR is possible but would seem offhand
to be the wrong thing to do. You might want to build your own irp with your
own PSECURITY_DESCRIPTOR rather than messing with the one handed to you.

Mark Roddy
Windows 2000/NT Consultant
Hollis Technology Solutions
www.hollistech.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Sudhir_Sambrani
Sent: Thursday, May 25, 2000 1:09 AM
To: NT Developers Interest List
Subject: [ntdev] Reg. IRP_MJ_SET_SECURTIY

Hi all,
The IRP_MJ_SET_SECURTIY has a PSECURITY_DESCRIPTOR in its
IoStackLocation’ parameters.

Can anybody tell me what is the data in the buffer at which the pointer is
pointing??

Is there in way in which we can extract the data stored at the buffer at
which this pointer is pointing?

Also is it possible if we can create our own security descriptor, fill in
the buffer & pass it to the lower level driver?

Thanks