Package: xmlsec1
Version: 1.2.6-1
Severity: important

Go to the examples directory, compile decrypt2 and decrypt3, and run
either one with the good parameters. For example:

testbox[examples] MALLOC_CHECK_=1 ./decrypt3 encrypt3-res.xml
malloc: using debugging hooks
Decrypted XML data:
<?xml version="1.0" encoding="UTF-8"?>
<!-- 
XML Security Library example: XML doc file encrypted with a session DES key 
(encrypt3 example). 
-->
<Envelope xmlns="urn:envelope">
  <Data>
        Hello, World!
  </Data>
</Envelope>

free(): invalid pointer 0x805f41f!
free(): invalid pointer 0x805f423!
free(): invalid pointer 0x805f428!
free(): invalid pointer 0x805f409!


If you don't set MALLOC_CHECK_, you get a core dump.

The error lies somewhere between the calls to
xmlSecReplaceNodeBuffer() made by the xmlSecEncCtxDecrypt() function
and xmlFreeDoc() done by the example itself. It goes too deep inside
libxml2 for me to debug.

I also tested fresh downloads of xmlsec1 (not from Debian), versions
1.2.5 through 1.2.8, all fail with the same behaviour, at the same
place.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-test1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages xmlsec1 depends on:
ii  libc6         2.3.2.ds1-22               GNU C Library: Shared libraries an
ii  libssl0.9.7   0.9.7-stable-SNAP-20040427 SSL shared libraries
ii  libxml2       2.6.20-1                   GNOME XML library
ii  libxmlsec1    1.2.6-1                    XML security library
ii  libxmlsec1-op 1.2.6-1                    Openssl engine for the XML securit
ii  libxslt1.1    1.1.14-1                   XSLT processing library - runtime 
ii  zlib1g        1:1.2.2-4                  compression library - runtime

xmlsec1 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to