[jira] [Resolved] (SANTUARIO-378) xml-security-c cannot initialise on a Windows system with mandatory user profiles

["Scott Cantor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SANTUARIO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor resolved SANTUARIO-378.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: C++ 1.7.2)
                   C++ 1.7.3

http://svn.apache.org/r1655511

I don't see any major risk to leaving it null, the Win APIs should just detect an invalid handle and fail later, and there aren't a lot of code paths involved.

Testing would be encouraged however.

> xml-security-c cannot initialise on a Windows system with mandatory user profiles
> ---------------------------------------------------------------------------------
>
>                 Key: SANTUARIO-378
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-378
>             Project: Santuario
>          Issue Type: Bug
>          Components: C++
>    Affects Versions: C++ 1.7.2
>         Environment: Windows with mandatory user profiles (eg: Citrix)
>            Reporter: John Elliott
>            Assignee: Scott Cantor
>             Fix For: C++ 1.7.3
>
>
> Under Windows, XSECPlatformUtils::Initialise() starts by creating a new WinCAPICryptoProvider. This fails at WinCAPICryptoProvider.cpp:127 when trying to create its key store:
> 		// Try to create
> 		if (!CryptAcquireContext(&m_provApacheKeyStore,
> 			s_xsecKeyStoreName,
> 			provRSAName,
> 			m_provRSAType,
> 			dwFlags | CRYPT_NEWKEYSET)) {
> 			throw XSECException(XSECException::InternalError,
> 				"WinCAPICryptoProvider() - Error obtaining generating internal key store for PROV_RSA_FULL");
> 		}
> The Windows error is NTE_TEMPORARY_PROFILE. 
> http://blogs.msdn.com/b/alejacma/archive/2007/10/23/rsacryptoserviceprovider-fails-when-used-with-mandatory-profiles.aspx explains that the RSA crypto provider does not allow keys to be stored when a mandatory profile is in use.
> Would it be practical to change behaviour in this case so that library initialisation does not fail, and the exception is thrown only if there is an attempt to use the key store?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)