Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 22 Jan 2014 23:31:24 +0000 (UTC)
From: "Demetrius Tsitrelis (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12690433.1390433466803.51279.1390433484607@arcas>
In-Reply-To: <JIRA.12690433.1390433466803@arcas>
References: <JIRA.12690433.1390433466803@arcas>
Subject: [jira] [Created] (CLOUDSTACK-5931) Hyper-V agent does not release
 logon handle
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Demetrius Tsitrelis created CLOUDSTACK-5931:
-----------------------------------------------

             Summary: Hyper-V agent does not release logon handle
                 Key: CLOUDSTACK-5931
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5931
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Hypervisor Controller
    Affects Versions: 4.3.0
            Reporter: Demetrius Tsitrelis


In the HypervResource project, in the Utils.DownloadCifsFileToLocalFile() method there is a call to LogonUser() to allocate a user token with new credentials.  This token is assigned to an instance of the WindowsIdentity class but is never explicitly deallocated.

It doesn't appear that the WindowsIdentity instance takes ownership of the token, however: http://msdn.microsoft.com/en-us/library/85yh2h4a.aspx states "Always release userToken by calling the Win32 API CloseHandle function".


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)