On Thu, Aug 07, 2008 at 02:33:35PM -0700, Juan Lang wrote: > > I guess I should elaborate on that. You can request any of the four > > parts of the security descriptor and pass NULL for the SD itself and > > Windows will return them without anyway to free the memory. > > I can see what MSDN says it does, but your tests don't check that > calling GetSecurityInfo with a non-null ppsidOwner, ppsidGroup etc. > and a null ppSecurityDescriptor is allowed. Because you're not > checking it, it looks like a bug.
These results were determined through tests that I ran on Windows. I don't think I included them with the conformance tests because I didn't think tests that leaked memory would be very good tests. I will send them in a separate patch since the implementation is still valid.
