SecHashEngine Doesn't work with newer version of libxml2

[csanders-git]

When using libxml2-2.9.3-1 SecHashingEngine didn't function properly
When using libxml2-2.7.6 SecHashingEngine works properly.

The exploration continues.

[csanders-git]

Looks like the break happened with 2.9.0
2.8.0 works and is the last version before 2.9.0

[csanders-git]

libxml2-2.9.0-rc0 does not work - so 2.8.0 is the last known working version

[csanders-git]

2.8-2.9DIFFS.txt

[csanders-git]

Check at msc_crypt.c:1081returns true when it shouldn't - and we return.

[csanders-git]

In functional version we skip #ifdef LIBXML2_NEW_BUFFER
Macro: LIBXML2_NEW_BUFFER

#define LIBXML2_NEW_BUFFER
Macro used to express that the API use the new buffers for xmlParserInputBuffer and xmlOutputBuffer. The change was introduced in 2.9.0.

[csanders-git]

xmlOutputBufferGetSize(output_buf) is returning 0

[csanders-git]

It appears xmlOutputBufferGetSize cannot be called on an output_buf after it has been flushed with xmlOutputBufferFlush(output_buf);

[csanders-git]

Seems like this originated here -> https://mail.gnome.org/archives/xml/2013-June/msg00006.html

[csanders-git]

5cf5ff0

[dune73]

Good writeup. Thanks.
Just to please the search-engine: It's SecHashEngine (not SecHashingEngine).

[dune73]

OK, tried to work around this, but no avail. Actually libxml2 and modsec rule version overlap and I am not totally sure which product is being described at every occurrence. Here is what I did.

• Compiled libxml2 2.7.8 -> OK
• Compiled apache 2.4.18 against libxml2 2.7.8 -> OK
• Compiled modsecurity 2.9.1 against libxml2 2.7.8-> OK -> But standard apache fails with execution error
• Compiled modsecurity 2.9.1 against apache-with-libxml2-2.7.8 and against libxml2 2.7.8 -> Compilation failure
• Compiled modsecurity 2.8.0 against standard apache -> OK -> But bug did not go away.

So I am a bit at loss here. What did I get wrong?

[victorhora]

Can't reproduce this issue with the current codebase of v2.

I believe commit a249574 should have fixed this already. Thanks.