Bug#919324: CVE-2018-20450 CVE-2018-20452

2019-01-29 Thread Jennifer Bryan
: > Thanks Jenny. In that case I am not planning any additional code changes, > just documentation and maybe tweaks to the build scripts. > > Sent from my iPad > > On Jan 29, 2019, at 11:47, Jennifer Bryan wrote: > > Yes, all is good. I had pulled libxls again yesterday after

Bug#919324: CVE-2018-20450 CVE-2018-20452

2019-01-29 Thread Jennifer Bryan
eared without warning. > > Sent from my iPad > > > On Jan 27, 2019, at 10:27, Dirk Eddelbuettel wrote: > > > > > > On 27 January 2019 at 09:25, Evan Miller wrote: > > | > > | > On Jan 26, 2019, at 23:09, Dirk Eddelbuettel wrote: > > | > >

Bug#919324: CVE-2018-20450 CVE-2018-20452

2019-01-26 Thread Jennifer Bryan
I'll still wait a bit to see if libxls can get to an official release soon. But readxl builds and passes tests everywhere with the current libxls, so that's good news: https://github.com/tidyverse/readxl/pull/543 -- Jenny On Sat, Jan 26, 2019 at 7:23 AM Evan Miller wrote: > > > On Jan 26, 201

Bug#919324: CVE-2018-20450 CVE-2018-20452

2019-01-24 Thread Jennifer Bryan
Thanks for the update and fixes, Evan! What sort of timeframe do you have in mind re: your official release? That affects how I think about timing a readxl release. I don't do them lightly but also want to get the fixes that address the CVEs into readxl sooner rather than later. -- Jenny On Thu