Date: Mon, 23 Jan 2017 23:14:19 -0800 From: Alan Coopersmith <alan.coopersmith@...cle.com> To: Pierre Ossman <ossman@...dio.se>, tigervnc-devel@...glegroups.com Cc: oss-security@...ts.openwall.com Subject: Re: [tigervnc-devel] Re: [tigervnc-announce] TigerVNC 1.7.1 On 01/23/17 12:34 AM, Pierre Ossman wrote: > On 22/01/17 07:25, Alan Coopersmith wrote: >> Is there a CVE assigned to this issue that we should use when passing this >> fix through to our packages/distros? I don't see one mentioned in the >> commit >> or pull requests: >> >> https://github.com/TigerVNC/tigervnc/commit/18c020124ff1b2441f714da2017f63dba50720ba >> >> >> https://github.com/TigerVNC/tigervnc/pull/399 >> > > Not to my knowledge, no. Thanks. Mitre - can a CVE be assigned for the above issue, as fixed in TigerVNC 1.7.1 ( https://github.com/TigerVNC/tigervnc/releases/tag/v1.7.1 )? -- -Alan Coopersmith- alan.coopersmith@...cle.com Oracle Solaris Engineering - http://blogs.oracle.com/alanc
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.