Re: textproc/libxml CVE-2016-4658 CVE-2016-5131

2016-12-30 Thread Antoine Jacoutot
On Fri, Dec 30, 2016 at 04:43:41PM +0100, Alexander Bluhm wrote: > On Fri, Dec 30, 2016 at 03:44:28PM +0100, Antoine Jacoutot wrote: > > Other than the github->git.gnome.org thingy, OK for me > > Fixed. > > > but could you explicitely > > set the revision for each subpackage? (i.e. REVISION-main,

Re: textproc/libxml CVE-2016-4658 CVE-2016-5131

2016-12-30 Thread Alexander Bluhm
On Fri, Dec 30, 2016 at 03:44:28PM +0100, Antoine Jacoutot wrote: > Other than the github->git.gnome.org thingy, OK for me Fixed. > but could you explicitely > set the revision for each subpackage? (i.e. REVISION-main, REVISION-python). libxml2mod.so contains only wrappers around the patched fun

Re: textproc/libxml CVE-2016-4658 CVE-2016-5131

2016-12-30 Thread Antoine Jacoutot
On Fri, Dec 30, 2016 at 03:32:47PM +0100, Alexander Bluhm wrote: > On Fri, Dec 30, 2016 at 12:54:59PM +0100, Simon Mages wrote: > > textproc/libxml is affected by those CVEs: > > CVE-2016-4658 > > CVE-2016-5131 > > > > Attached is a updated version of the port which includes the patches > > menti

Re: textproc/libxml CVE-2016-4658 CVE-2016-5131

2016-12-30 Thread Alexander Bluhm
On Fri, Dec 30, 2016 at 12:54:59PM +0100, Simon Mages wrote: > textproc/libxml is affected by those CVEs: > CVE-2016-4658 > CVE-2016-5131 > > Attached is a updated version of the port which includes the patches mentioned > above. I have - changed revision to 0, - checked that patches contain the

textproc/libxml CVE-2016-4658 CVE-2016-5131

2016-12-30 Thread Simon Mages
Hi textproc/libxml is affected by those CVEs: CVE-2016-4658 CVE-2016-5131 Patches are available here: https://git.gnome.org/browse/libxml2/commit/?id=c1d1f7121194036608bf555f08d3062a36fd344b https://git.gnome.org/browse/libxml2/commit/?id=9ab01a277d71f54d3143c2cf333c5c2e9aaedd9e Attached is a up