From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42522)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fH6jU-00069V-7U
	for guix-patches@gnu.org; Fri, 11 May 2018 08:01:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fH6jO-0006cx-N0
	for guix-patches@gnu.org; Fri, 11 May 2018 08:01:08 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:49323)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1fH6jO-0006cq-KW
	for guix-patches@gnu.org; Fri, 11 May 2018 08:01:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fH6jO-00034R-Cz
	for guix-patches@gnu.org; Fri, 11 May 2018 08:01:02 -0400
Subject: [bug#30801] Add opencv
Resent-Message-ID: <handler.30801.D30801.152604002111749@debbugs.gnu.org>
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
References: <20180313175809.7d782c1a@alma-ubu> <87po45rqx5.fsf@gnu.org>
	<20180401002649.37231b47@alma-ubu> <87a7unglrh.fsf@gnu.org>
	<20180507203547.3ae3cb35@alma-ubu> <878t8sxzdi.fsf@gnu.org>
	<20180511115124.0f8ed3d9@alma-ubu>
Date: Fri, 11 May 2018 14:00:05 +0200
In-Reply-To: <20180511115124.0f8ed3d9@alma-ubu> ("=?UTF-8?Q?Bj=C3=B6rn_?=
	=?UTF-8?Q?H=C3=B6fling?="'s message of
	"Fri, 11 May 2018 11:51:24 +0200")
Message-ID: <87bmdmpflm.fsf@gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-patches/>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?= <bjoern.hoefling@bjoernhoefling.de>
Cc: 30801-done@debbugs.gnu.org

Hello!

Bj=C3=B6rn H=C3=B6fling <bjoern.hoefling@bjoernhoefling.de> skribis:

> On Thu, 10 May 2018 00:01:13 +0200
> ludo@gnu.org (Ludovic Court=C3=A8s) wrote:

[...]

>> =E2=80=98guix lint=E2=80=99 reports this:
>>=20
>>   gnu/packages/image-processing.scm:201:2: opencv@3.4.1: probably
>> vulnerable to CVE-2018-7712, CVE-2018-7713, CVE-2018-7714
>>=20
>> Could you take a look?  It could be that 3.4.2 is around the corner
>> and we=E2=80=99ll just update at that point; if not, we may have to apply
>> upstream patches for these issues.
>
> While finally linting, I noticed these too. OpenCV claims this is not
> an issue:
>
> https://github.com/opencv/opencv/issues/10998
>
> Should we mention it somewhere in the code? Is there a formal process
> to hide or comment specific CVEs?

The developer=E2=80=99s reasoning makes sense to me (IOW, the CVEs should be
against the applications that don=E2=80=99t handle exceptions properly rath=
er
than against OpenCV itself.)

You can use the =E2=80=98lint-hidden-cve=E2=80=99 property to explicitly hi=
de them.
Please add a comment with the URL above as well.

Thanks,
Ludo=E2=80=99.