|From:||Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>|
|To:||Magnus Hagander <magnus(at)hagander(dot)net>|
|Cc:||Stephen Frost <sfrost(at)postgresql(dot)org>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Akio Iwaasa <aki-iwaasa(at)vt(dot)jp(dot)nec(dot)com>|
|Subject:||RE: PostgreSQL 2018-05-10 Security Update Release|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> From: Magnus Hagander [mailto:magnus(at)hagander(dot)net]
> It seems RedHat have changed the CVSS vector from the one that we submitted
> to them. The PostgreSQL Security Team assigned the score and vector as is
> listed on the PostgreSQL website, so that is the correct one as standing.
Sorry, It seems I had misunderstood that.
> I have pinged the RedHat team to see if they did this intentionally,or if
> it was a mistake.
It would be appreciated if you could share the response from the RedHat team.
Thanks and best regards,
Dang Minh Huong
NEC Solution Innovators, Ltd.
|Next Message||Vladimir Borodin||2018-05-30 13:22:48||Open sourcing Odyssey: scalable connection pooler|
|Previous Message||David Fetter||2018-05-27 19:05:17||== PostgreSQL Weekly News - May 27 2018 ==|
|Next Message||PG Bug reporting form||2018-05-29 07:32:38||BUG #15213: unable to login on PostgreSQL by postgres user|
|Previous Message||PG Bug reporting form||2018-05-28 00:30:21||BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation|