Click here to Skip to main content
Click here to Skip to main content
Add your own
alternative version

The Windows Access Control Model Part 4

, 7 Sep 2005
The final article in the access control series presents a guide to the access control editor and its associated ISecurityInformation interface.
filepermsbox-1_11.zip
Filepermsbox-1.11.exe
filepermsbox111.zip
release
FilePermsBox.dll
FilePermsBox.exe
FilePermsBox.Interop.dll
filepermsboxsrc.zip
Frontend
FilePermsBox.exe.manifest
InnoForm.isf
SetupFpms.iss
NetWrapper
FilePermsBox.Interop.tlb
FPermBoxKey.snk
FilePermsBox.Interop.dll
LockKey.ico
FilePermsBoxDLL
165.avi
FilePermsDll.def
FilePermsDll.manifest
FilePermsDll64.def
/**
*	This code is by OShah. all code will have the following licence.
*	Copyright Shexec32. All code bears the following licence:
**/

/**
*	Copyright Shexec32 2004-2005. All rights reserved.
*
*	THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF
*	ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED
*	TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
*	PARTICULAR PURPOSE.
**/

#ifndef REENABLE_ERRORS_H
#define REENABLE_ERRORS_H
#pragma once

#pragma warning (pop)
/** Although the 3rd party code cannot compile with such aggressive
*	warnings, it doesn't give us an excuse to disable warnings.
*	Therefore, reenable all warnings (disabled from disable_errors.h)...
*	except the following:
**/

#pragma warning (disable:6309)
/** argument is null; does not adhere to function specification.
*	These warnings typically occur when we call GetNamedSecurityInfo(),
*	which expect NULL pointers to be passed in. The docs for
*	GetNamedSecurityInfo() explicitly statethat passing NULLs is OK.
*	As you should know by now, if the docs say it, it must be right (if
*	it isn't, Windows gets hacked so it is right).
**/

#pragma warning (disable:6014)
/** Code may leak memory.
*	These warnings occur in the QueryInterface() functions. Now, it
*	certainly looks like we'd leak memory in QueryInterface(), but due
*	to one of the pecularities in COM (they call it feature), we
*	don't. We allocate the memory in QueryInterface(), and delete it in
*	Release().
*
*	I always knew that COM was a POS. Now the C++ compiler agrees with me.
**/

#pragma warning (disable:6258)
/** Using TerminateThread() does not allow proper thread clean up. Yes,
*	there is one place where we use TerminateThread, but we only use it
*	in an extreme circumstance (so extreme, that the user would have
*	killed the thread themselves).
*
*	We send the worker thread a cleanup message, via the fully supported
*	WM_CLOSE. This initiates the complete thread cleanup which Should
*	finish in less than a second. Once the thread handle gets signalled,
*	we wake back up and finish off. Only in the extreme circumstance where
*	it takes over 10 minutes to shutdown, do we kill it. If the worker
*	thread hangs, we hang; so it comes to the same thing whether the user
*	kills the thread or we kill the thread.
**/

#endif /* REENABLE_ERRORS_H */

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

Share

About the Author

oshah
Web Developer
United States United States
Mr. Shah is a reclusive C++/C# developer lurking somewhere in the depths of the city of London. He learnt physics at Kings' College London and obtained a Master in Science there. Having earned an MCAD, he teeters on the brink of transitioning from C++ to C#, unsure of which language to jump to. Fortunately, he also knows how to use .NET interop to merge code between the two languages (which means he won't have to make the choice anytime soon).
 
His interests (apart from programming) are walking, football (the real one!), philosophy, history, retro-gaming, strategy gaming, and any good game in general.
 
He maintains a website / blog / FAQ / junk at shexec32.serveftp.net, where he places the best answers he's written to the questions you've asked. If you can find him, maybe you can hire Mr. Shah to help you with anything C++[/CLI]/C#/.NET related Smile | :) .

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.141223.1 | Last Updated 7 Sep 2005
Article Copyright 2005 by oshah
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid