Re: [sqlite] CVE's opened on 3.30.1 status

2019-12-25 Thread Richard Hipp
On 12/25/19, Dominique Pellé wrote: > > According to https://sqlite.org/draft/releaselog/3_31_0.html > SQLite-3.31 is scheduled for 2019-12-31. > I have idea how accurate this date is though. :-) I made that estimate on 2019-10-29. Now that we are closer to the date, I can confidently predict

Re: [sqlite] CVE's opened on 3.30.1 status

2019-12-25 Thread Dominique Pellé
Raitses, Alex wrote: > Thanks a lot for the prompt response, > As far as I found in Fossil repository fixes for all CVE's , > excepting erroneously submitted CVE-2019-19646, were merged to Fossil. > Can you please estimate next official release of SQLite including these fixes? According to

Re: [sqlite] CVE's opened on 3.30.1 status

2019-12-24 Thread Raitses, Alex
- From: drhsql...@gmail.com On Behalf Of Richard Hipp Sent: Tuesday, December 24, 2019 6:31 PM To: SQLite mailing list Cc: Raitses, Alex Subject: Re: [sqlite] CVE's opened on 3.30.1 status On 12/24/19, Raitses, Alex wrote: > Hi, > Can you please update on status of the following CVE’s sub

Re: [sqlite] CVE's opened on 3.30.1 status

2019-12-24 Thread Richard Hipp
On 12/24/19, Raitses, Alex wrote: > Hi, > Can you please update on status of the following CVE’s submitted on 3.30.1? > CVE’s link to patches references GitHub branch, however I could find > corresponding submits to Fossil repository. > CVE’s list: >

[sqlite] CVE's opened on 3.30.1 status

2019-12-24 Thread Raitses, Alex
Hi, Can you please update on status of the following CVE’s submitted on 3.30.1? CVE’s link to patches references GitHub branch, however I could find corresponding submits to Fossil repository. CVE’s list: https://nvd.nist.gov/vuln/detail/CVE-2019-19244