Re: [arch-general] JasPer vulnerabilities

2016-03-07 Thread Harrison Wells
On 07-Mar-2016 5:59 PM, "Levente Polyak" wrote: > > On 03/07/2016 01:04 PM, Harrison Wells wrote: > > Haven't reported in security list before. Should I just repost my previous > > message? > > It's a announcement only mailing list, discussions should go here > (arch-general) and most of the time

Re: [arch-general] JasPer vulnerabilities

2016-03-07 Thread Levente Polyak
On 03/07/2016 01:04 PM, Harrison Wells wrote: > Haven't reported in security list before. Should I just repost my previous > message? It's a announcement only mailing list, discussions should go here (arch-general) and most of the time we also notice and read that. However to directly report or as

Re: [arch-general] JasPer vulnerabilities

2016-03-07 Thread Harrison Wells
Haven't reported in security list before. Should I just repost my previous message? On 07-Mar-2016 5:28 PM, "LoneVVolf" wrote: > On 07-03-16 10:55, Harrison Wells wrote: > >> Is the package JasPer in extra repo vulnerable to CVE-2016-1577, >> CVE-2016-2089 and CVE-2016-2116? I noticed that the ve

Re: [arch-general] JasPer vulnerabilities

2016-03-07 Thread LoneVVolf
On 07-03-16 10:55, Harrison Wells wrote: Is the package JasPer in extra repo vulnerable to CVE-2016-1577, CVE-2016-2089 and CVE-2016-2116? I noticed that the version number of JasPer is same in Debian, Ubuntu and Arch, i.e. 1.900.1. Debian and Ubuntu seem to have updated/patched it, is Arch not v

[arch-general] JasPer vulnerabilities

2016-03-07 Thread Harrison Wells
Is the package JasPer in extra repo vulnerable to CVE-2016-1577, CVE-2016-2089 and CVE-2016-2116? I noticed that the version number of JasPer is same in Debian, Ubuntu and Arch, i.e. 1.900.1. Debian and Ubuntu seem to have updated/patched it, is Arch not vulnerable to it? With regards, Harrison W