Il 16/09/15 15:50, Papaiakos, Nikos (Nokia - GR/Athens) ha scritto:
Hello Alberto,

Thanks for your quick response.
As far as I understand, we have to use (at least) Xerces 2.9 (as the link you 
mentioned, refers that this version solves the issue)

The "fixed in 2.9" means that the fix is in the xercesc-2 branch, and will be delivered in the next version (that will never be released, btw). So if you need the fix, you cannot download a pre-built package, but you need to retrieve the code from the xercesc-2 branch and compile it. Unless you rely on a package mantained by someone else, who took care of picking the code for the fix and applied to the 2.8-GA code..
Also, in order to clarify: The Xerces 2.8 itself is compatible with x64-bit. 
Right?

Yes.

Alberto


Regards,
Nikos

-----Original Message-----
From: EXT Alberto Massari [mailto:albertomass...@tiscali.it]
Sent: Wednesday, September 16, 2015 2:03 PM
To: c-users@xerces.apache.org
Subject: Re: Xerces C++ 2.8

Hi Nikos,
the corresponding bug is https://issues.apache.org/jira/browse/XERCESC-1885
If you pick the latest version from the 2.8 branch it has the fix.
As for the 64-bit version, the projects have a x64 configuration, so you
can build them and expect to work as the 32 bit does.

Alberto

Il 16/09/15 12:25, Papaiakos, Nikos (Nokia - GR/Athens) ha scritto:
Hello,

I know that this version of Xerces C++ is unsupported.
However, I would like to know, if possible, the following:
          -We use Xerces in our 32-bit application in 32-bit machines (Windows 
Server 2008). Can we use it also in x64-bit (windows server 2012)? Is there any 
compatibility issue?
          -I have found a medium vulnerability (CVE-2009-1885). Is there any 
other security issue for this version. Are these issues solved in a latter 
version?

Thanks in advance

Regards,
Nikos








--
-----------------------------------------
Lucia Riccardi & Alberto Massari
Via Prasca 19/5
16148 Genova
Italia
Tel.: (010) 3771653
E-mail: lucia_albe...@libero.it
Web: http://www.massari.org

Reply via email to