[xml] Entering freeze for libxml2-2.9.8

2018-01-22 Thread Daniel Veillard
Hi all, so we are starting the freeze for the next release of libxml2. I have tagged the release candidate 1 in Git and pushed a signed tarball and rpms to the usual place: ftp://xmlsoft.org/libxml2/ I updated my machine with the release candidate, it would be good if other interested peo

Re: [xml] [xslt] Time for some releases

2018-01-22 Thread Daniel Veillard
On Mon, Jan 22, 2018 at 04:57:20PM +0100, Nick Wellnhofer wrote: > On 21/01/2018 07:22, Daniel Veillard wrote: > > I think it's time for a new set of releases, > > I failed to push in the last 2 months and a number of patches > > have accumulated since november, so I think entering freeze on Mon

Re: [xml] Heap use after free in parser.c

2018-01-22 Thread Jay Civelli via xml
On Mon, Jan 22, 2018 at 7:53 AM, Nick Wellnhofer wrote: > On 08/01/2018 22:43, Jay Civelli wrote: > >> On Mon, Jan 8, 2018 at 11:27 AM, Nick Wellnhofer > > wrote: >> >> On 02/01/2018 20:08, Jay Civelli via xml wrote: >> >> We ran into a heap use after free

Re: [xml] Time for some releases

2018-01-22 Thread Nick Wellnhofer
On 21/01/2018 07:22, Daniel Veillard wrote: I think it's time for a new set of releases, I failed to push in the last 2 months and a number of patches have accumulated since november, so I think entering freeze on Mon or Tuesday, then having rc2 around end of week for a release early around 29-

Re: [xml] Heap use after free in parser.c

2018-01-22 Thread Nick Wellnhofer
On 08/01/2018 22:43, Jay Civelli wrote: On Mon, Jan 8, 2018 at 11:27 AM, Nick Wellnhofer > wrote: On 02/01/2018 20:08, Jay Civelli via xml wrote: We ran into a heap use after free in Chromium http://crbug.com/793715 that

Re: [xml] [PATCH] Check hex or decimal entity for overflow

2018-01-22 Thread Nick Wellnhofer
On 09/01/2018 00:55, Joel Hockey wrote: Updated patch with XML_ERR_INVALID_CHAR. Should be fixed with https://git.gnome.org/browse/libxml2/commit/?id=60dded12cbf1705927803c5ed615a7a0132aebbd As noted previously, this only affects "recovery" mode. The commit addresses the issue at an earlier