Re: Build problems

[Berin Lautenbach <be...@ozemail.com.au>]

Vincent,

Firstly - I Am Not A Lawyer!  My first advice to all and sundry is to 
always make sure for yourself.

RSA should be fine - it went out of patent a few years back.  DSA and 
SHA1 are also OK.

MD-5 might be a problem (can't remember, but I have something niggling 
in the back of my mind).

The library can pretty much use any of RSA/DSA/HMAC for signature and 
SHA-1/MD-5 for digest operations.

Cheers,
	Berin

Vincent Finn wrote:
> I got OpenSSL and everything builds and xtest runs perfectly as far as I can
> tell
> Thanks.
> 
> I do have one more question though
> it is about licensing
> I know that there is no problem with the licence for xsec, xerces and
> OpenSSL
> but on the OpenSSL webpage it mentions that you may need license 
> depending on which algorithm is used for the encryption e.g. RSA
> which algorithm does xsec use?
> and do I need to licence it?
> 
> 	Thanks, Vin
> 
> 
>>-----Original Message-----
>>From: Berin Lautenbach [mailto:berin@ozemail.com.au]
>>Sent: 31 July 2003 08:04
>>To: 'security-dev@xml.apache.org'
>>Subject: Re: Build problems
>>
>>
>>Vincent,
>>
>>Xerces 2.2 should be fine.
>>
>>Could you try running xtest?  That uses HMAC with "secret" as 
>>a key to 
>>run a few tests of the system.  You don't need to pass it anything.
>>
>>What compiler are you using?  It almost looks like the C14n 
>>sample can't 
>>find the xerces install?
>>
>>You might also want to link in OpenSSL once you have everything 
>>compiling - it's far more tested than the Windows Crypto API.
>>
>>Cheers,
>>	Berin
>>
>>Vincent Finn wrote:
>>
>>>Hi,
>>>
>>>I just downloaded the library and can't get all the 
>>
>>projects (in particular
>>
>>>the samples) with it to build
>>>
>>>I have xerces 2.2 on the machine, 
>>>I assume this is the correct version since there were far 
>>
>>more errors with
>>
>>>2.1 or 2.3 
>>>
>>>I am building without Xalan or OpenSSL
>>>
>>>I have put a few of the linker errors below and the compile 
>>
>>error from the
>>
>>>samples
>>>
>>>only 3 projects build, xsec_lib, templatesign and xtest
>>>
>>>I haven't tried actually running them yet since I haven't 
>>
>>got a key to use
>>
>>>yet
>>>
>>>possibly these projects are irrelevant to me but I want to make sure
>>>
>>>All I need to do is take a DOMDocument, sign it (the whole 
>>
>>thing) and write
>>
>>>it out
>>>and then take that file, verify it, decrypt it and get a DOMDocument
>>>
>>>Anyone know what is wrong?
>>>and do I need to worry about it?
>>>
>>>	Thanks, Vin
>>>
>>>c14n.obj : error LNK2001: unresolved external symbol 
>>
>>"public: virtual void
>>
>>>__thiscall 
>>
>>xercesc_2_2::AbstractDOMParser::TextDecl(unsigned short const *
>>
>>>const,unsigned short const * const)"
>>>(?TextDecl@AbstractDOMParser@xercesc_2_2@@UAEXQBG0@Z)
>>>c14n.obj : error LNK2001: unresolved external symbol 
>>
>>"public: virtual void
>>
>>>__thiscall xercesc_2_2::AbstractDOMParser::startExtSubset(void)"
>>>(?startExtSubset@AbstractDOMParser@xercesc_2_2@@UAEXXZ)
>>>c14n.obj : error LNK2001: unresolved external symbol 
>>
>>"public: virtual void
>>
>>>__thiscall xercesc_2_2::AbstractDOMParser::startIntSubset(void)"
>>>(?startIntSubset@AbstractDOMParser@xercesc_2_2@@UAEXXZ)
>>>c14n.obj : error LNK2001: unresolved external symbol 
>>
>>"public: virtual void
>>
>>>__thiscall xercesc_2_2::AbstractDOMParser::startAttList(class
>>>xercesc_2_2::DTDElementDecl const &)"
>>>
>>
>>(?startAttList@AbstractDOMParser@xercesc_2_2@@UAEXABVDTDElemen
>>tDecl@2@@Z)
>>
>>>compile errors
>>>xml-security-0.2.0\src\samples\IOStreamOutputter.hpp(88): 
>>
>>error C2061:
>>
>>>syntax error : identifier 'XERCES_CPP_NAMESPACE_QUALIFIER'
>>>xml-security-0.2.0\src\samples\IOStreamOutputter.hpp(88): 
>>
>>error C2805:
>>
>>>binary 'operator <<' has too few parameters
>>>
>>
>