Am using xml-security-c-1.1.0 suite. Doing ENCRYPT_3DES_CBC as block-encrypt generates an encrypted xml with <CipherValue> having line breaks after every 64 bytes.
I have to exchange data with an exisiting application that gives me the CipherValue without line breaks. This gives me inter-operability problem. Is there any way I can get away with this. Any flag that can be set which over-rides this limitation ? I remember doing the same while doing Base64 Encoding in Perl where you set a flag and it over-rides the default line break after 64 chars. Thanks Satya -----Original Message----- From: Berin Lautenbach [mailto:[EMAIL PROTECTED] Sent: Saturday, January 01, 2005 9:33 AM To: security-dev@xml.apache.org Subject: Re: Problem building xml-security-c-1.1.0 suite on Solaris 2.8 Satya, Can you send me (not the list :>) a copy of the config.log that configure should have generated? Cheers, Berin Satyaprabh kathooria wrote: > Hi > > I am getting problem building xml-security-c-1.1.0 suite on Solaris 2.8. > Running configure itself exits with an error for XERCESCROOT (Refer > console messages below). However my XERCESCROOT is pointing to the > correct location of Xerces 2.3 installation. > > I am using gcc 3.2 on Solaris 2.8 box. > > Where am I going wrong? > > Regards > Satya > > $ ./configure --prefix=/home/porting/satya/dsig/project > checking for gcc... gcc > checking for C compiler default output file name... a.out checking > whether the C compiler works... yes checking whether we are cross > compiling... no checking for suffix of executables... > checking for suffix of object files... o checking whether we are using > the GNU C compiler... yes checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed checking > whether we are using the GNU C++ compiler... yes checking whether g++ > accepts -g... yes checking for a BSD-compatible install... > /home/porting/satya/dsig/xml-security-c-1.1.0/src/install-sh > checking whether ln -s works... yes > checking for gawk... no > checking for mawk... no > checking for nawk... nawk > checking for autoconf... true > checking how to run the C preprocessor... gcc -E checking how to run > the > C++ preprocessor... g++ -E checking for Intel compiler disguised as > GNU... no checking for floor in -lm... yes checking for egrep... egrep > checking for ANSI C header files... yes checking for sys/types.h... > yes checking for sys/stat.h... yes checking for stdlib.h... yes > checking for string.h... yes checking for memory.h... yes checking for strings.h... > yes checking for inttypes.h... yes checking for stdint.h... no > checking for unistd.h... yes checking for unistd.h... (cached) yes > checking direct.h usability... no checking direct.h presence... no > checking for direct.h... no checking build system type... > sparc-sun-solaris2.8 checking host system type... sparc-sun-solaris2.8 > checking for Xerces 2.x headers in XERCESCROOT/src... no checking for > Xerces 2.x headers in system includes... configure: error: Xerces 2.0 > not found. Ensure XERCESCROOT points to base directory of Xerces and > Xerces 2.0 or later is available > > >
