Mailing-List: contact dev-help@impala.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@impala.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAC-pSX25RTQNYhxtqe+Et65m02SThP1_B5cfq-WMihb18W3GXQ@mail.gmail.com>
References: <CAFeypE1f=KSJO7iwniEAZqhHRia4Q51WV1EdCFcTFsq9NcEhbA@mail.gmail.com>
 <CAC-pSX25RTQNYhxtqe+Et65m02SThP1_B5cfq-WMihb18W3GXQ@mail.gmail.com>
From: Roman Kulyk <rom.kulyk@gmail.com>
Date: Wed, 17 May 2017 14:26:20 +0300
Message-ID: <CAFeypE16vnewiCr8Bg9piDWEokF63ks8At9UL8TVRH7E5RNm8A@mail.gmail.com>
Subject: Re: CVE for IMPALA-5005
To: dev@impala.incubator.apache.org
Content-Type: multipart/alternative; boundary="94eb2c0555b8b55f26054fb68e13"
archived-at: Wed, 17 May 2017 11:26:26 -0000

--94eb2c0555b8b55f26054fb68e13
Content-Type: text/plain; charset="UTF-8"

Jim,

Thank you for answer. Could you please tell when you are planning release
that includes IMPALA-5005 fix (maybe you can tell a month)?

Roman

2017-05-16 21:27 GMT+03:00 Jim Apple <jbapple@cloudera.com>:

>  we release CVEs after a release that includes the fixes is produced.
>
> On Tue, May 16, 2017 at 3:42 AM, Roman Kulyk <rom.kulyk@gmail.com> wrote:
> > Hi all!
> >
> > I have a question about CVE (Common Vulnerabilities and Exposures) for
> > IMPALA-5005 <https://issues.apache.org/jira/browse/IMPALA-5005>. Could
> you
> > please tell when you are planning publically announce this vulnerability
> > and assign a CVE? If you already done it, could you please share link?
> >
> > Thanks!
> > Roman
>

--94eb2c0555b8b55f26054fb68e13--