Hello,
I'm currently exactly in the situation described by Microsoft at kb/3148821
I modified registry keys as described by Microsoft, but I still have error while processing signed xml.
Below is the StackTrace
à MS.Internal.IO.Packaging.CustomSignedXml.RequireNCNameIdentifier()
à MS.Internal.IO.Packaging.CustomSignedXml.GetIdElement(XmlDocument document, String idValue)
à System.Security.Cryptography.Xml.Reference.CalculateHashValue(XmlDocument document, CanonicalXmlNodeList refList)
à System.Security.Cryptography.Xml.SignedXml.CheckDigestedReferences()
à System.Security.Cryptography.Xml.SignedXml.CheckSignature(X509Certificate2 certificate, Boolean verifySignatureOnly)
à MS.Internal.IO.Packaging.XmlDigitalSignatureProcessor.Verify(X509Certificate2 signer)
à System.IO.Packaging.PackageDigitalSignature.Verify(X509Certificate signingCertificate)
Microsoft proposed no registry key in relation to RequireNCNameIdentifier to modify.
I also applied complementary registry modification proposed by Anders Abel (breaking-changes-to-signedxml-in-ms16-035), but I still have the same error.
Did somebody else encounter this issue? any idea how to solve it (without uninstall the security update)?
Best Regards,
Prosper