Version 1.4
* The *SecurityContext* classes have been renamed to *ImpersonationScope*
* The SecurityContext class has been renamed to CallbackImpersonationScope
* New ImpersonationScope class, which accepts a username/password combination
* The AcquireCredentialCallbackEventHandler class has been removed in favor of the EventHandler<AcquireCredentialEventArgs> class
* Privilege Management: The Privileges and Privilege classes allows the manipulation of privileges held by a WindowsIdentity.
* New IdentityResolver. Basically, the same functionality as IdentityReference.Translate(). However, a remote computer can be used for the translation process. Additionally, the type of the account type (user, group, computer, etc) is returned

Version 1.3
* The ImpersonationContext class has been renamed to SecurityContext
* The DialogImpersonationContext class has been renamed to DialogSecurityContext
* The DialogImpersonationContextInfo class has been renamed to DialogSecurityContextInfo
* The CmdLineImpersonationContext class has been renamed to CmdLineSecurityContext

Version 1.2
* Added a Confirm and Invalidate method the the SecurityContext. This is useful when generic credentials are queried from the user instead of Windows credentials (for example to authenticate to a remote webserver). In this case you can manually confirm or invalidate the credential.
* Added a Username and Password property to the SecurityContext class. Again this is important when working with generic credentials.
* Added a new class: SecureStringDecryptor. This class allows you to get a byte array containing the decrypted content of a SecureString instance. But be careful when using this class. Do not convert the byte array to a string instance. Do not make a copy the byte array. You should use this class as described in this article only. Otherwise, most of the security advantages of the SecureString class are gone. You have been warned!
