[xmlsec] Newer binaries for xmlsec - Please

[EdShallow]

The template I used was posted to the list yesterday under my name.

Cheers and thanks again for working on the wekend  ; )

Ed

On Sun, Jun 19, 2011 at 5:32 PM, EdShallow <ed.shallow at gmail.com> wrote:

> Thanks I see that from the code.
>
> OK, good news and bad news.
>
> Good news:
> - my test suite works for crypto=openssl
> - most of the test suite works for crypto=mscrypto when KeyName is all
> characters
>
> Bad news:
> - any certificate the non-alphanumerics in the CN= do not work.I get a
> ...see below
>
> Can I trouble you to try compile with Unicode=no and perhaps post both ?
>
> Cheers,
> Ed
>
> C:\XMLSec>xmlsec sign --crypto mscrypto --output
> inout/edsigned-enveloped.xml tmpl/tmpl-EPM-sign-enveloped.xml
> func=xmlSecMSCryptoKeyDataAdoptCert:file=..\src\mscrypto\certkeys.c:line=448:obj=unknown:subj=CryptAcquireCertificatePrivateKey:error=4:crypto
> library function failed: ;last error=-2146
> 893799 (0x80090019);last error msg=The keyset is not defined.
>
> func=xmlSecMSCryptoCertAdopt:file=..\src\mscrypto\certkeys.c:line=885:obj=unknown:subj=xmlSecMSCryptoPCCDataAdoptPCC:error=1:xmlsec
> library function failed: ;last error=-2146893799 (0x8
> 0090019);last error msg=The keyset is not defined.
>
> func=xmlSecMSCryptoKeysStoreFindKey:file=..\src\mscrypto\keysstore.c:line=539:obj=unknown:subj=xmlSecMSCryptoCertAdopt:error=1:xmlsec
> library function failed: ;last error=-2146893799 (0
> x80090019);last error msg=The keyset is not defined.
>
> func=xmlSecKeysMngrGetKey:file=..\src\keys.c:line=1370:obj=unknown:subj=xmlSecKeysMngrFindKey:error=1:xmlsec
> library function failed: ;last error=-2146885628 (0x80092004);last error
> msg
> =Cannot find object or property.
>
> func=xmlSecDSigCtxProcessKeyInfoNode:file=..\src\xmldsig.c:line=871:obj=unknown:subj=unknown:error=45:key
> is not found: ;last error=-2146885628 (0x80092004);last error msg=Cannot
> find o
> bject or property.
>
> func=xmlSecDSigCtxProcessSignatureNode:file=..\src\xmldsig.c:line=565:obj=unknown:subj=xmlSecDSigCtxProcessKeyInfoNode:error=1:xmlsec
> library function failed: ;last error=-2146885628 (0
> x80092004);last error msg=Cannot find object or property.
>
> func=xmlSecDSigCtxSign:file=..\src\xmldsig.c:line=303:obj=unknown:subj=xmlSecDSigCtxSigantureProcessNode:error=1:xmlsec
> library function failed: ;last error=-2146885628 (0x80092004);las
> t error msg=Cannot find object or property.
>
> Error: signature failed
> Error: failed to sign file "tmpl/tmpl-EPM-sign-enveloped.xml"
>
>
> On Sun, Jun 19, 2011 at 5:19 PM, Igor Zlatković <igor at zlatkovic.com>wrote:
>
>> I forgot to say, sorry for the waiting.
>>
>> I did not remove the code within ifdefs, I removed the #ifdef and #endif
>> lines. The code within those ifdefs was included in the compilation that
>> way.
>>
>> I compiled with unicode=yes (which was the default). The ifdefs only
>> mentioned MinGW, not Unicode.
>>
>> I a still using the XP DDK. But not for much longer. I will at some
>> point drop Microsoft compiler in favour of GCC. Newer MS compilers are
>> harder to tweak to make them use the system runtime.
>>
>> Ciao,
>> Igor
>>
>>
>>
>> On 19/06/11 23:03, EdShallow wrote:
>> > Yes, I did something similar. I noticed the xxx_s functions exclusively
>> > within MinGW and Unicode ifdef's.
>> > Did you just remove all the code within those 2 ifdef's?
>> > If so use would have had to compile with Unicode=no.
>> > Is that what you did?
>> > Thanks again for the Father's Day gift ; )
>> > Ed
>> > P.S Are you still compiling with the DDK?
>> >
>> > On Jun 19, 2011 4:52 PM, "Igor Zlatković" <igor at zlatkovic.com
>> > <mailto:igor at zlatkovic.com>> wrote:
>> >> Hi Ed,
>> >>
>> >> I uploaded the latest release, 1.1.18. Please check whether it works
>> for
>> >> you.
>> >>
>> >> The newest source for mscrypto backend uses strcpy_s and wcscpy_s
>> >> runtime functions which are not available on my XP SP3. Frankly, the
>> >> system runtime (msvcrt.dll) doesn't export them. This source may work
>> >> with the VS runtime, but not with system runtime. I used the same fix
>> >> that was meant for MinGW, see the beginning of the file crypto.c. That
>> >> did it, but I don't know whether that is cool.
>> >>
>> >> Ciao,
>> >> Igor
>> >>
>> >>
>> >> On 18/06/11 05:25, EdShallow wrote:
>> >>> Hello Igor,
>> >>>
>> >>> I have valiantly tried to get my Windows binaries working but
>> >>> without luck. Although I get a clean compile and link with nmake, I am
>> >>> still getting strange errors with my binaries. I have no problems with
>> >>> your 1.13 but need the mscrypto algorithms in 1.15 and above.
>> >>>
>> >>> I am kindly asking that you indulge me and the others waiting for
>> >>> updated xmlsec binaries.
>> >>>
>> >>> Thanks in advance,
>> >>> --
>> >>> Ed's Contact Information:
>> >>> Mobile Phone: 613-852-6410
>> >>> Gmail: ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>
>> > <mailto:ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>>
>> >>> VOIP Address: 107529 at sip.ca1.voip.ms <mailto:107529 at sip.ca1.voip.ms>
>> > <mailto:107529 at sip.ca1.voip.ms <mailto:107529 at sip.ca1.voip.ms>>
>> >>> VOIP DID#: 613-458-5004
>> >>> Skype ID: edward.shallow
>> >>> Home Phone: 613-482-2090
>> >>>
>> >>
>>
>>
>
>
> --
> Ed's Contact Information:
> Mobile Phone: 613-852-6410
> Gmail: ed.shallow at gmail.com
> VOIP Address: 107529 at sip.ca1.voip.ms
> VOIP DID#: 613-458-5004
> Skype ID: edward.shallow
> Home Phone: 613-482-2090
>
>


-- 
Ed's Contact Information:
Mobile Phone: 613-852-6410
Gmail: ed.shallow at gmail.com
VOIP Address: 107529 at sip.ca1.voip.ms
VOIP DID#: 613-458-5004
Skype ID: edward.shallow
Home Phone: 613-482-2090
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.aleksey.com/pipermail/xmlsec/attachments/20110619/08c7f60c/attachment-0001.html>