To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=41748


User mmi changed the following:

                  What    |Old value                 |New value
================================================================================
               Assigned to|mmi                       |mt
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Tue Feb  1 20:26:41 -0800 
2005 -------
Hi,

The reason has been found.

In libxml 2.6.17, the default SAX parser is SAX2, but in the previous libxml
2.5.11, it is SAX1. Because some xmlsecurity functions rely on the libxml SAX1
parser, so it crashes.

To fix this bug, two things need to be done:

1) configure the libxml module to include the SAX1 support.

I noticed that the default setting of libxml2 has enabled SAX1, but to avoid the
SAX1 feature is removed from the default setting in any future version, I
suggest to include the --with_sax1=yes (sax1=yes for windows) option explicitly
into makefile.mk of libxml2 module.

2) modify xmlsecurity module, to enforce the SAX parser to be SAX1 version.

I have changed it in xmlsec08, please use the following command to update
xmlsecurity/source/xmlsec/saxhelper.cxx in your cws:

cvs update -j1.1.1.1.24.2 -j1.1.1.1.24.3 saxhelper.cxx


Let me know the result.

Thanks.

Michael



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to