[xmlsec] Re: problem encrypting when using Windows 2000 ?

[Meg Morgan]

Thank you both for your time and attention to this matter.
I am on my way out the door but will study your responses
more tomorrow.  When do you anticipate the "big new release"?
That will help me plan my work, or investigate other workarounds.

Thanks again Igor and Aleksey
meg

Aleksey Sanin wrote:
> 
> Igor,
> 
> Thanks for looking into this! I believe that there is a problem with
> exporting pointers from dlls. In xmlsec I have static objects in the
> DLL and I export pointers to these objects. The error Meg and
> some other folks have is caused by the fact that these pointers are
> NULL in the application (or point to garbage in some cases).
> AFAIK, libxml and libxslt does not use such technique and there is
> no surprise that your binaries work just fine for these libraries :)
> When it's a simple and clear operation on *nix, it seems to be a problem
> on Windows because of the compiler(s), compiler options or whatever.
> I am working on fixing this but this will have to wait till the big new
> release because of binary compatibility issues.
> 
> Aleksey
> 
> Igor Zlatkovic wrote:
> 
> > Hi Meg,
> >
> > I tried and tried, but wasn't able to reproduce that error.
> >
> > I use a slightly newer compiler than you do. As far as I know, the
> > binaries produced by that compiler are fully compatible with those
> > produced by VC 6. There should be no problems.
> >
> > However, there are some, obviously. Things might go good if you
> > recompile xmlsec with VC 6 but I fear that is not the root of the
> > problem. After all, libxml and libxslt binaries on my site are made
> > with the same compiler, are being downloaded fifty times a day in
> > average and many who use them do it with VC 6. The problem never
> > occured in a package other than xmlsec.
> >
> > I believe that the best way is to find the real source of the peril.
> > If it is in the xmlsec code, it must be fixed. If you did something
> > wrong in your code, then few others are obviously doing the same and
> > it should be discovered what that is. Finally, if the compiler is the
> > problem, then I'll start making binaries with VC 6.
> >
> > I have produced xmlsec 0.0.11 with VC 6 for you to test. You can get
> > it at
> > http://zlatkovic.com/projects/libxml/libxmlsec-0.0.11.win32.vc6.zip
> > Check if that one works.
> >
> > If you have code which demonstrates the error for me to use locally
> > for debugging, it would be very helpful.
> >
> > Ciao,
> > Igor
> >
> >
> > Meg Morgan wrote:
> >
> >> Greetings,
> >>
> >> I understand from Alexsey that this problem has been reported before.
> >> I am using your binaries and developing a windows application with
> >> MS Visual C++ 6.0.  When I call xmlSecEncryptMemory I get an error:
> >>
> >> xmlSecTransformFind <..\src\transforms.c:331>: error 10:  :
> >>   href=http://www.w3.org/2001/04/xmlenc#tripledes-cbc
> >>
> >>
> >> Alexsey writes:
> >> "Let me guess, you are using Windows.
> >> Most likely you are using Igor's Windows binaries with MS VC 6.0.
> >> There were reported similar problems in this situation and the best
> >> advise I can give is to try to recompile everything by you "native"
> >> compiler."
> >>
> >> Is there any solution other than for me to compile under Windows myself?
> >>
> >> Thank you for your help,
> >> meg
> >>
> >
> > _______________________________________________
> > xmlsec mailing list
> > xmlsec at aleksey.com
> > http://www.aleksey.com/mailman/listinfo/xmlsec

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Meg Morgan                           425/739-2534
meg at votehere.net                   http://www.votehere.net